[
https://issues.jboss.org/browse/AS7-1273?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-1273:
-----------------------------------
If the persistence unit doesn't specify a datasource (jta or non-jta) and there
isn't a default datasource configured in standalone.xml/domain.xml, we should not
deploy the persistence unit definition (just ignore it with a logged warning).
At least, that seems like the right thing to do with regard to this case. Target code
site to fix is
org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.addPuService()
Applications (or their libraries) containing persistence units with
the connection defined inline via properties cause deployment failure.
------------------------------------------------------------------------------------------------------------------------------------------
Key: AS7-1273
URL:
https://issues.jboss.org/browse/AS7-1273
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.0.0.Final, 7.1.0.Alpha1
Reporter: Justin Wyer
Assignee: Scott Marlow
Labels: as7, jpa
Persistence units defined as follows
https://github.com/droolsjbpm/jbpm/blob/master/jbpm-human-task/src/main/r...
causes deployment to fail due to the fact that no <jta-data-source> or
<non-jta-data-source> is present, but none should be present as the datasource has
been defined via the properties.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira