[jboss-jira] [JBoss JIRA] (WFLY-3531) JPA persistence unit services should start completly before sub-deployments reach the next deployment phase

[Scott Marlow (JIRA)]

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

Scott Marlow commented on WFLY-3531:
------------------------------------

potential fix is at https://github.com/scottmarlow/wildfly/tree/WFLY-3531_pu_next_phase_deps

> JPA persistence unit services should start completly before sub-deployments reach the next deployment phase
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-3531
>                 URL: https://issues.jboss.org/browse/WFLY-3531
>             Project: WildFly
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JPA / Hibernate
>            Reporter: Scott Marlow
>            Assignee: Scott Marlow
>             Fix For: 9.0.0.Alpha1
>
>
> This is about EAR deployments that contain multiple sub-deployments.  Currently, EJB jar sub-deployments may still be starting their JPA persistence units while other sub-deployments move ahead (in parallel) to other deployment phases (which can cause the entity classes to be loaded before the persistence provider has been registered with the class file transformer for the persistence unit).  
> Each deployment/sub-deployment should set the NEXT_PHASE_DEP on the persistence unit service (see current phaseContext.addToAttachmentList(Attachments.NEXT_PHASE_DEPS, puServiceName) in PersistenceUnitServiceHandler).  For this to work, each deployment/subdeployment should set NEXT_PHASE_DEPS during the FIRST_MODULE_USE phase for each pre-determine persistence unit service name).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)