[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=13618429#comment-13618429 ] 

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

Option #4, introduce lazy starting of the persistence unit (EntityManagerFactory) on first use of EM or EMF.  Obviously, bytecode enhancement would not work and there would be an application delay waiting for the persistence unit deployment to complete.  

Perhaps some other things would also not work, but since not everything can work together, this might help some users.  It could also reduce memory usage, in that unused persistent units wouldn't be deployed.

> 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
>
> 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.5.0#75005)