Applications should be able to inject a persistence context/unit from a separate deployment by using a fully scoped (appname#puname) reference ---------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-9034 URL: https://issues.jboss.org/browse/JBAS-9034 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public(Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Scott Marlow Fix For: 7.0.0.Beta2 This is mostly about creating unit tests to ensure that it works and continues to work.

Applications should be able to inject a persistence context/unit from a separate deployment by using a fully scoped (appname#puname) reference ---------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-9034 URL: https://issues.jboss.org/browse/JBAS-9034 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public(Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.Beta2 A few things needs to happen for this to work. 1. Deployments that use container managed JPA support, need to be recognized by the JPADependencyProcessor. JPADependencyProcessor will inject the JPA dependencies into the deployment, so that it can access JPA stuff. 2. JPADependencyProcessor currently runs during DEPENDENCIES phase but we don't recognize annotations (JPAAnnotationParseProcessor) until later during the POST_MODULE phase. Either we need to change JPAAnnotationParseProcessor to not use Attachments.COMPOSITE_ANNOTATION_INDEX (so we can move JPAAnnotationParseProcessor to the PARSE phase) or Attachments.COMPOSITE_ANNOTATION_INDEX needs to be built during the PARSE phase (again, allowing moving of JPAAnnotationParseProcessor to the PARSE phase).

Applications should be able to inject a persistence context/unit from a separate deployment by using a fully scoped (appname#puname) reference ---------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-9034 URL: https://issues.jboss.org/browse/JBAS-9034 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public(Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.Beta2 A few things needs to happen for this to work. 1. Deployments that use container managed JPA support, need to be recognized by the JPADependencyProcessor. JPADependencyProcessor will inject the JPA dependencies into the deployment, so that it can access JPA stuff. 2. JPADependencyProcessor currently runs during DEPENDENCIES phase but we don't recognize annotations (JPAAnnotationParseProcessor) until later during the POST_MODULE phase. Either we need to change JPAAnnotationParseProcessor to not use Attachments.COMPOSITE_ANNOTATION_INDEX (so we can move JPAAnnotationParseProcessor to the PARSE phase) or Attachments.COMPOSITE_ANNOTATION_INDEX needs to be built during the PARSE phase (again, allowing moving of JPAAnnotationParseProcessor to the PARSE phase).

Applications should be able to inject a persistence context/unit from a separate deployment by using a fully scoped (appname#puname) reference ---------------------------------------------------------------------------------------------------------------------------------------------- Key: AS7-564 URL: https://issues.jboss.org/browse/AS7-564 Project: Application Server 7 Issue Type: Sub-task Affects Versions: 7.0.0.Beta1 Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.Beta2 A few things needs to happen for this to work. 1. Deployments that use container managed JPA support, need to be recognized by the JPADependencyProcessor. JPADependencyProcessor will inject the JPA dependencies into the deployment, so that it can access JPA stuff. 2. JPADependencyProcessor currently runs during DEPENDENCIES phase but we don't recognize annotations (JPAAnnotationParseProcessor) until later during the POST_MODULE phase. Either we need to change JPAAnnotationParseProcessor to not use Attachments.COMPOSITE_ANNOTATION_INDEX (so we can move JPAAnnotationParseProcessor to the PARSE phase) or Attachments.COMPOSITE_ANNOTATION_INDEX needs to be built during the PARSE phase (again, allowing moving of JPAAnnotationParseProcessor to the PARSE phase).