[
https://issues.jboss.org/browse/AS7-5015?page=com.atlassian.jira.plugin.s...
]
Scott Marlow resolved AS7-5015.
-------------------------------
Resolution: Rejected
I could recreate the failure, thanks for the test case. To get the test to pass, I
changed as7/standalone/configuration/standalone.xml:
From:
<spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>
To:
<spec-descriptor-property-replacement>true</spec-descriptor-property-replacement>
And then start the AS:
./standalone.sh "-Dtest.ds=java:jboss/datasources/ExampleDS"
That passed. I didn't know about the above property setting but know I do.
Using variable in persistence.xml <jta-data-source> leads to
deployment-dependencies-error
------------------------------------------------------------------------------------------
Key: AS7-5015
URL:
https://issues.jboss.org/browse/AS7-5015
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP)
Environment: domain-full-ha
Reporter: Stephan Pelikan
Assignee: Scott Marlow
Attachments: testbean-with-variables.ear, testbean-without-variables.ear
Using variables in persistence.xml works (see AS7-3195). But if used within tag
jta-data-source an error is show during deployment:
"jboss.persistenceunit.\"pdfWhitelabelServer.ear/pdfWhitelabelServer.jar#ipadDomain\"
Missing[jboss.naming.context.java.\"${ipadserverds.jndipath}\"]",
(pdfWhitelabel is our product; ipadDomain is the name of the persistence-unit;
${ipadserverds.jndipath} is the variable defined as start-parameter for a node).
The goal is to deploy one deployment to different server groups (one server group for
each customer) and the software should use different datasources in each server group for
jpa ( neccessary to avoid resource-dependences between customer-instances).
According to our needs we use domain-mode but for completeness it doesn't work using
standalone either.
--
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