rs List <[EMAIL PROTECTED]>
> > Subject: Re: Embedding Tomcat with intra-app Servlets
> >
> >
> > I'm not sure this solves my problem...
> >
> > If I pull my Servlet out of my application's code then the instance will
> > be constructed and lo
On Fri, 2 Nov 2001, Todd Wright wrote:
> Date: Fri, 2 Nov 2001 15:56:44 -0400
> From: Todd Wright <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: Tomcat Users List <[EMAIL PROTECTED]>
> Subject: Re: Embedding Tomcat with intra-app
One appraoch for data sharing is to structure the application as
separate web-apps and use beans in the request (response, session
context, whatever) to pass information back and forth.
I currently have a web-app that gets the original request, populates
the request with needed beans and include
t;
> I would recommend you implement the application logic as a standard
> servlet, in its own class, and separate the startup/shutdown issues out to
> their own class. There is nothing to be gained by combining them.
>
> Craig
>
> On Fri, 2 Nov 2001, Todd Wright wrote:
> &
ed by combining them.
Craig
On Fri, 2 Nov 2001, Todd Wright wrote:
> Date: Fri, 2 Nov 2001 12:25:23 -0400
> From: Todd Wright <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Embedding Tomcat with intra-app Servlets
I'd like to embed Tomcat within my Java application, but where some Servlet
requests would *directly* call into my running application's code (+data).
The current "EmbededTomcat" support seems to be aimed at launching a
stand-alone Tomcat that only supports file contexts, with no callback su
