Skip to content

#3551 Log warning for use of mapping column to Class#3698

Merged
rbygrave merged 1 commit into
masterfrom
feature/3551
Nov 10, 2025
Merged

#3551 Log warning for use of mapping column to Class#3698
rbygrave merged 1 commit into
masterfrom
feature/3551

Conversation

@rbygrave

Copy link
Copy Markdown
Member

I think it was a mistake for Ebean to support Class<?> from a security perspective. Instead, Ebean should just use a String <-> Varchar and leave if up to the application to take that String and convert it to a class [and then that potential Class initialisation is owned by the application code and all security considerations around that are owned by the application code].

I think it was a mistake for Ebean to support Class<?> from a security perspective. Instead, Ebean should just use a String <-> Varchar and leave if up to the application to take that String and convert it to a class [and then that potential Class initialisation is owned by the application code and all security considerations around that are owned by the application code].
@rbygrave rbygrave self-assigned this Nov 10, 2025
@rbygrave rbygrave linked an issue Nov 10, 2025 that may be closed by this pull request
@rbygrave rbygrave merged commit 5b04d6e into master Nov 10, 2025
1 check passed
@rbygrave rbygrave deleted the feature/3551 branch November 10, 2025 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Primitives and nested class problem with Class column type

1 participant