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

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

Currently, at the root deployment level, we are tracking all of the contained persistence units (from top + sub level), of which every component will have a dependency on, so that any component could depend on any persistence unit in the application.  

Why didn't reproducer-ear-0.1.ear/reproducer-ejb2.jar#pu2 start?  

{code}
service jboss.persistenceunit."reproducer-ear-0.1.ear/reproducer-ejb2.jar#pu2" (missing) dependents: [service jboss.deployment.subunit."reproducer-ear-0.1.ear"."reproducer-ejb.jar".component.StatelessBean1.START, service jboss.deployment.unit."reproducer-ear-0.1.ear".WeldStartService] 
{code}

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