[jira] [Commented] (CAUSEWAY-3959) [JPA] Build framework-provided Entities using Static Weaving
[ https://issues.apache.org/jira/browse/CAUSEWAY-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18056594#comment-18056594 ] Andi Huber commented on CAUSEWAY-3959: -- Midway through converting abstract classes to interfaces, I'm seeing now meta-model issues when launching the demo app. This needs separate investigation. Looks like types are now introspected, which were not before. For debugging these kind of problems (which I've seen in the past), it would be nice to have some sort of logging, that tracks what triggered introspection of a specific type. > [JPA] Build framework-provided Entities using Static Weaving > > > Key: CAUSEWAY-3959 > URL: https://issues.apache.org/jira/browse/CAUSEWAY-3959 > Project: Causeway > Issue Type: New Feature > Components: Persistence JPA >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 4.0.0 > > > We could perhaps provide additional Maven artifacts distinguished by a > classifier (in terms of Maven coordinates). > Alternatively just figure out how corresponding build instructions look like > and then document the build process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAUSEWAY-3959) [JPA] Build framework-provided Entities using Static Weaving
[ https://issues.apache.org/jira/browse/CAUSEWAY-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054895#comment-18054895 ] Andi Huber commented on CAUSEWAY-3959: -- There is yet an unsolved problem, that is DomainObject and DomainObjectAnnotations are not allowed on interfaces. That is a framework restriction. However, we could introduce a marker interface EntityInterface say, which would be the explicit exception to this rule and hints the framework to expect concrete implementations to be of BeanSort ENTITY. > [JPA] Build framework-provided Entities using Static Weaving > > > Key: CAUSEWAY-3959 > URL: https://issues.apache.org/jira/browse/CAUSEWAY-3959 > Project: Causeway > Issue Type: New Feature > Components: Persistence JPA >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 4.0.0 > > > We could perhaps provide additional Maven artifacts distinguished by a > classifier (in terms of Maven coordinates). > Alternatively just figure out how corresponding build instructions look like > and then document the build process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAUSEWAY-3959) [JPA] Build framework-provided Entities using Static Weaving
[ https://issues.apache.org/jira/browse/CAUSEWAY-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054886#comment-18054886 ] Andi Huber commented on CAUSEWAY-3959: -- see also https://github.com/apache/causeway/pull/3375 > [JPA] Build framework-provided Entities using Static Weaving > > > Key: CAUSEWAY-3959 > URL: https://issues.apache.org/jira/browse/CAUSEWAY-3959 > Project: Causeway > Issue Type: New Feature > Components: Persistence JPA >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 4.0.0 > > > We could perhaps provide additional Maven artifacts distinguished by a > classifier (in terms of Maven coordinates). > Alternatively just figure out how corresponding build instructions look like > and then document the build process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAUSEWAY-3959) [JPA] Build framework-provided Entities using Static Weaving
[ https://issues.apache.org/jira/browse/CAUSEWAY-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054882#comment-18054882 ] Andi Huber commented on CAUSEWAY-3959: -- For static weaving even to work, we need to satisfy some requirements, that is, entities and their relations (including abstract classes) must be in the same artifact. Or one needs to do the static weaving process in one blow over the entire multi-module project between COMPILE and PACKAGING phases of the Maven build. For SecMan entities and their abstract super classes (ApplicationUser, ApplicationRole, ...) are not in the same module. If by any chance we can convert those 4 abstract super classes into interfaces, static weaving could work, in a standard build process using https://github.com/ethlo/eclipselink-maven-plugin > [JPA] Build framework-provided Entities using Static Weaving > > > Key: CAUSEWAY-3959 > URL: https://issues.apache.org/jira/browse/CAUSEWAY-3959 > Project: Causeway > Issue Type: New Feature > Components: Persistence JPA >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 3.6.0, 4.0.0 > > > We could perhaps provide additional Maven artifacts distinguished by a > classifier (in terms of Maven coordinates). > Alternatively just figure out how corresponding build instructions look like > and then document the build process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
