This problem I have in almost each project! The "tomcat" JNDI solution is a way that we have tried in a project. For unit test, we have initialized our own JNDI context, for starting without tomcat.
http://blog.artifact-software.com/tech/?p=58
If you have a larger environment, you will be in the "JNDI hell" really soon ,-) The server.xml isn't a clear way to handle a big set of properties for different environments and many projects.
A database will be the better solution. But then maybe you should have an administration inferface other than sql and a view where you can view the properties for a project in a certain environment (don't forget the security than!).
Misgivings about the database could be handled by exporting the properties at startup or at deployment! Maybe an in memory db is a more failsafe way. But if you have problems with the failure safety of your database, you have a problem anyway ;-)
Fredy
Keine Kommentare:
Kommentar veröffentlichen