One of my ongoing maintenance reducers for my current set of projects
has been to share the same configuration file in all my projects,
letting JNDI point to the right things at the right times.
However, it'd be cool if my application didn't attempt to access a
data source definition until it actually needed it. Right now, I
have to define JNDI definitions for all databases even if the
underlying application will never use the node.
I do note that the actual connection to the database is deferred until
it's first used. What's the feasability of also deferring the JNDI
request until it's also needed?
I admit I haven't tried to look into the source yet -- being lazy
today -- in case that someone can give me a quick "don't bother"
before spending any time on it ;)
And if it is feasable, how do others feel about this change? I
suppose I could make a subclass of JNDIDataSourceFactory in the worse
case, make it a config option in the second case, and make it the only
behavior in the best case :)
This archive was generated by hypermail 2.0.0 : Fri May 05 2006 - 09:59:47 EDT