Should mention use of openjpa.ConnectionFactory2Name and
openjpa.ConnectionFactoryName in a testing section
-----------------------------------------------------------------------------------------------------------
Key: OPENJPA-1436
URL: https://issues.apache.org/jira/browse/OPENJPA-1436
Project: OpenJPA
Issue Type: Bug
Components: docs
Affects Versions: 1.2.1
Reporter: David M. Karr
I suppose a higher-level point that should be made is that the doc should have
a section on "testing", covering issues specific to OpenJPA that facilitate or
hinder testing. The particular point I wanted to make is that if you need to
override the "jta-data-source" or "non-jta-data-source" in a test (or
anywhere), the properties "openjpa.ConnectionFactory2Name" and/or
"openjpa.ConnectionFactoryName" need to be set, very likely to the empty string.
For instance, my application uses "non-jta-data-source" to connect to a JNDI
datasource in WebLogic, which connects to Oracle. However, my database tests
use an embedded instance of Apache Derby. In my test setup, I pass properties
to the EntityManagerFactory creation that specifies the database connection,
but I had to know to set those two properties (just the "2" one, in my case) to
empty strings, to cause it to not try to look up the datasource from JNDI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
