J
Jerry Camel
On the WebLogic side of our development team, we use JNDI and access
datasources that are defined outside the actual application. This is an
advantage in several ways... Not the least is becasue our DBA's insist on
having different names for the development and production versions of the
databases. So I've had to recompile or reconfigure my web apps in order to
move them to production. To me this is a bit against the entire purpose of
development. If I have to change my code to move it to production, then
that code hasn't been tested... etc.. etc.. etc..
So... It seems to me there must be a way to implement an external
datasource as we do with WebLogic and java. Then, all I'd have to do is
update the database name in the datasource and my application would require
no changes at all.
Can someone point me in the right direction to do this? Thanks.
Jerry
datasources that are defined outside the actual application. This is an
advantage in several ways... Not the least is becasue our DBA's insist on
having different names for the development and production versions of the
databases. So I've had to recompile or reconfigure my web apps in order to
move them to production. To me this is a bit against the entire purpose of
development. If I have to change my code to move it to production, then
that code hasn't been tested... etc.. etc.. etc..
So... It seems to me there must be a way to implement an external
datasource as we do with WebLogic and java. Then, all I'd have to do is
update the database name in the datasource and my application would require
no changes at all.
Can someone point me in the right direction to do this? Thanks.
Jerry