I believe you and Martin are saying the same thing. I could do that however I would need my jar file to be in $TOMCAT_HOME/shared/lib probably. I can't have each different web app starting new instances of the services. Services are only started once be Tomcat Server.
I thought maybe it was possible to add something to server.xml to get a component to startup. Perhaps I'd have it implement a Tomcat Interface but I could do that and then have it only start once per Tomcat Instance. Either way I need my jar in $TOMCAT_HOME/shared/lib. That is the one I put it in right? Not $TOMCAT_HOME/common/lib? Mike Wannamaker -----Original Message----- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: July 17, 2006 12:39 PM To: Tomcat Users List Subject: Re: Tomcat Not An App Server Mike, > What I've done is ripped out our core services from our internal app server > and provided an app server connector layer. The idea is that we'll be able > to plug into any app server like container. Our own internal, JBoss, > WebSphere, Tomcat??? > > That is the idea. So we have customers that may have tomcat installed and > perhaps they would like to utilize that instead of installing another app > server. That is perfectly reasonable. Here's a suggestion: create a new webapp that doesn't actually have any servlets. Just create a ContextListener that responds to START and STOP requests, and use the listener to startup your services. web.xml in each webapp can specify the order of servlets coming into service... I'd imagine that Tomcat can be configured to load this "services" webapp before all other webapps are loaded, so that those services are available. Would this meet your needs? -chris --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
