[jboss-jira] [JBoss JIRA] (WFLY-9516) JPA deployer adding cross sub deployment dependencies when multiple persistence units deployed

[Scott Marlow (Jira)]

    [ https://issues.jboss.org/browse/WFLY-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649343#comment-13649343 ] 

Scott Marlow commented on WFLY-9516:
------------------------------------

Not much of an update, to share, just some more thoughts.

Avoiding breaking of existing application compatibility/Java EE compliance is an issue issue with the current POC.  I have some rough ideas of how we could break these things (compat/Java EE 8 compliance) possibly, in a future Jakarta EE release, which seems like the likely best (although slow) path forward.

Some ideas:

1. Remove runtime JPA byte code enhancing of entity classes and instead switch to build-time only (with a full recompile of classes needed for each upgrade to a new version of said Jakarta EE (e.g. 10) implementation).

2.  Change DataSources (including per app DS, like DataSourceDefinition) to always be available early in deployment, as the JPA persistence unit needs the DS right away.

Having (1) might be enough to properly do (lazy) on demand deployment of the persistence unit(s), however, if we could also do (2), that would cover more use cases (e.g. DataSourceDefinition support).



> JPA deployer adding cross sub deployment dependencies when multiple persistence units deployed
> ----------------------------------------------------------------------------------------------
>
>                 Key: WFLY-9516
>                 URL: https://issues.jboss.org/browse/WFLY-9516
>             Project: WildFly
>          Issue Type: Bug
>          Components: JPA / Hibernate
>    Affects Versions: 11.0.0.Final
>            Reporter: Brad Maxwell
>            Assignee: Scott Marlow
>            Priority: Major
>
> If an ear contains two EJB sub deployments which each contain a Persistence Unit and a Stateless EJB which injects the PU that is in its jar using @PersistenceContext.  There is a dependency being added where in the Stateless EJB from one deployment depends on the PU from the other jar.  It appears this is happening after this bug fix WFLY-1531
> {code}
> app.ear
>  - ejb-with-pu1.jar
>  - ejb-with-pu2.jar
> {code}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)