[
https://issues.jboss.org/browse/AS7-1273?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-1273:
-----------------------------------
I made a few code changes that need to get merged into AS7 master git repo. Until then, a
datasource name has to be specified in the persistence unit definition.
I tried to put a test case together using the persistence.xml settings linked above. The
problem is that Hibernate needs a dependency on the JDBC driver module. To hack around
that, I manually updated the as7/modules/org/hibernate/main/module.xml dependencies to
include "com.h2database.h2". I don't think I need to solve that part of the
problem, for this jira.
I will commit the changes made so far, so you can proceed forward and let us know if you
get stuck again.
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.Beta1, 7.0.0.Final
Reporter: Justin Wyer
Assignee: Scott Marlow
Labels: as7, jpa
Fix For: 7.0.2.Final
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