Hi,
So while we could put all the classes into common/lib and use a singleton pattern, I wouldn't have a way to cleanly shut down the service on app server shutdown (I could be wrong here).
You could use a JVM shutdown hook. At least that's portable and not Tomcat-specific.
Another alternative would be to externalize the service itself onto a separate server, so you don't need to worry about shutting it down at all ;)
Well, that's kind of what we do now. We expose the service via Hessian, so that all webapps can access it (and avoid classloading issues of implementation classes). I was hoping to avoid the overhead and expose as regular classes via JNDI.
Seth
-- <a href="http://www.picklematrix.net/foaf.rdf";>Seth Ladd's FOAF</a> <a href="http://www.foaf-project.org/";>What is FOAF?</a>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
