Hi,
Why go through all this? The point of the JNDI Resources part of the
Servlet Specification is to allow portable interaction with external
resources. Your approach loses all the portability (it's
Tomcat-specific) without gaining much of anything. You could do the
same stuff in your webapp,
Shapira, Yoav wrote:
Hi,
Why go through all this? The point of the JNDI Resources part of the
Servlet Specification is to allow portable interaction with external
resources. Your approach loses all the portability (it's
Tomcat-specific) without gaining much of anything. You could do the
same
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
Shapira, Yoav wrote:
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.
On Mon, Dec 13, 2004 at 08:50:18AM -1000, Seth Ladd wrote:
: 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
