You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using JPMS, MethodHandles.publicLookup()/MethodHandles.lookup() as currently used by ebean require a user to add an exports my.package directive to allow ebean to access the fields/methods/constructors of entities/DTOs.
The way around this is to pass a MethodHandles.Lookup from the entity/DTO class's module for ebean to use. I'm thinking we could create a new interface:
In this way, ebean can gain free reign to access the fields/methods/constructors of entities/DTOs without needing exports/opens directives from the user.
When using JPMS,
MethodHandles.publicLookup()
/MethodHandles.lookup()
as currently used by ebean require a user to add anexports my.package
directive to allow ebean to access the fields/methods/constructors of entities/DTOs.The way around this is to pass a
MethodHandles.Lookup
from the entity/DTO class's module for ebean to use. I'm thinking we could create a new interface:And have the querybean generator generate an implementation that can be service loaded.
In this way, ebean can gain free reign to access the fields/methods/constructors of entities/DTOs without needing
exports
/opens
directives from the user.Related to #3530
Would like to get #3528 merged before I start on this
The text was updated successfully, but these errors were encountered: