A "work-around" of sorts seems to be to not use a datasource. But that's bad
practice, I can get away with it because my application doesn't take heavy
traffic. But if I don't use a jta datasource and just connect to the
database directly then it works fine.
So
<property name="openjpa.ConnectionURL"
value="jdbc:oracle:thin:@server:1530:schema" />
<property name="openjpa.ConnectionDriverName"
value="oracle.jdbc.driver.OracleDriver" />
<property name="openjpa.ConnectionUserName" value="user" />
<property name="openjpa.ConnectionPassword" value="pass" />
</properties>
instead of
<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
<properties>
<property name="openjpa.DataCache" value="true"/>
<property name="openjpa.RemoteCommitProvider" value="sjvm"/>
<property name="openjpa.Log" value="DefaultLevel=WARN, Tool=INFO"/>
<property name="openjpa.TransactionMode" value="managed"/>
</properties>
--
View this message in context:
http://n2.nabble.com/Two-OpenJPA-Applications-in-the-same-container-tp4686242p4693652.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
