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

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

{quote}Why does JPA sometimes start in INSTALL and sometimes start in POST_MODULE?{quote}
Hibernate can only register its class file transformer during the POST_MODULE phase, so that Hibernate can rewrite entity classes.  It is too late for Hibernate to register class file transformers during the INSTALL phase, as the application classes will have already been loaded during the INSTALL phase (I think by Weld).  Applications that disable the persistence unit two phase start (via persistence unit hint "wildfly.jpa.twophasebootstrap=false"), will suffer from slower application performance as a result.



> 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)