Investigate the removal of JPA sections in AS7 standalone.xml ------------------------------------------------------------- Key: SWITCHYARD-514 URL: https://issues.jboss.org/browse/SWITCHYARD-514 Project: SwitchYard Issue Type: Task Components: component-bpel, component-bpm, configuration, deployment, distribution, openshift Reporter: David Ward Fix For: 0.3 The work done for SWITCHYARD-480 adds the jBPM Console to the AS7 release distribution. This resource was the starting place for that work: http://kverlaen.blogspot.com/2011/07/jbpm5-on-as7-lightning.html One of the steps says, "I got an error with my persistence.xml and JPA2 so I disabled JPA2 scanning by commenting out the JPA module (org.jboss.as.jpa) and subsystem (urn:jboss:domain:jpa:1.0) in the standalone.xml configuration file." This could cause problems for riftsaw (used by the BPEL Component), which needs JPA2. It is possible that step wasn't necessary to do, and could cause problems for OpenShift deployments anyways, so we should investigate if we can add those JPA sections back into the AS7 standalone.xml without harming the jBPM Console. (Developer Note: The removal of the sections was done via the standalone.xsl file.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira