James, Does your JDBCResources differ greatly from the one that is in Commons-resources already? (I'm trying to remember which version of CR I checked out but I cant heh) i.e. does it take advantage of any container connection pooling etc? The one I see in cr basically does a connection to the db via the standard drivermanager methods, and shoves them into a properties file.
The biggest reason I can ever see to use a db vs a file is for relatively real time updates of the message resources. The use case being that some "admin" user can change the messages via some interface (whether that be web or isql, or whatever) and then those changes are propagated to the web application almost automatically, or at least within some time period. On the one I wrote I went for lazy loading of the properties at request time for this reason, and it has a timeout that the webapp developer could set to allow for a variable timeout. Flow was basically check the cache, is the cache valid? Yes - return the message No - invalidate the cache entry and lookup the message in the db, place "new" message in cache, and return the message. I mainly wrote it as an example of how to extend the struts MessageResources and implement your own custom one. Since I mainly use full j2ee app servers I decided on a JNDI lookup to the DS instead of drivermanager type stuff. (plus with the lazy loading it helps to use a connection pool :) Anyway just wondering. (You know... comparing code sort of) Al --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
