[jboss-jira] [JBoss JIRA] (AS7-5015) Using variable in persistence.xml <jta-data-source> leads to deployment-dependencies-error
[
https://issues.jboss.org/browse/AS7-5015?page=com.atlassian.jira.plugin.s...
]
Stephan Pelikan commented on AS7-5015:
--------------------------------------
Thank you for this hint. I tried it in my domain-environment and it works fine. I
didn't know about this configuration but even the name of it describes the solution
perfectly.
There are only two things left which may be solved or not - its up to you:
1. The documentation
http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6...
should be adapted - it only talks of ejb-jar.xml. But I would have give it a try if I
had found this documentation during my fact-finding.
2. Why it works for other places within persistence.xml - even if
"spec-descriptor-property-replacement" is false? As mentioned above I tried to
switch a hibernate-property (show_sql) using the same technique and it did work. This made
me thinking that everything has been configured well.
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