I agree Andrus, however I'm not comfortable with having a username &
password in a properties file unless encrypted.
Now the XMLPoolingDataSourceFactory in the Modeler caters for a password
encoder, which is great.
However the database I'm using has a default transaction isolation level of
READ_COMMITED which I would like to change.
I can't seem to do this with the XMLPoolingDataSourceFactory, but the
DBCPDataSourceFactory can.
The problem though is that the username and password are in plain text with
this factory.
So I'm going to have to "hack" one of them ....
RFE: If there was a
org.apache.cayenne.configuration.Constants.TRANSACTION_ISOLATION property
then you could just put that into the Constants.PROPERTIES_MAP for the
XMLPoolingDataSourceFactory to use.
Thanks, regards
Jurgen
-----Original Message-----
From: Andrus Adamchik
Sent: Thursday, March 13, 2014 8:09 AM
To: [email protected]
Subject: Re: DBCPDataSourceFactory
On Mar 12, 2014, at 8:50 PM, [email protected] wrote:
Yip, that's what I was using in the Modeler but the username and pass have
to be in a properties file and I was hoping that there was a simple
alternative.
Usually the problem with specifying password (and other settings) in the
Modeler is that they are different between your dev environment and final
deployment environment. So while properties are not as simple as using UI,
it is a sensible alternative that will let you change those without
unpacking your deployment artifacts, etc.
Andrus
