Hello All,
This is a simular question I asked on the Tomcat mailing list and never got
a reply. I was hoping someone could give me some good input on this topic
from this list.
If I have a process that needs to run within Tomcat&Struts to communicate
with a remote server, and that process needs
Sean,
You would probably not write the task as a Servlet. Instead, as part of your
startup you'd put the task in application scope. Remember that Servlets/JSPs
that talk to the task are going to do so from different threads (potentially at
the same time). The task would probably manage its own
t;
Sent: Thursday, May 03, 2001 10:31 AM
Subject: Servlets, Beans, Struts, and Threading
> Hello All,
>
> This is a simular question I asked on the Tomcat mailing list and never
got
> a reply. I was hoping someone could give me some good input on this topic
> from this list.
>
thread of
execution.
Any insight you, Paul, or anyone else could give here would be greatly
appreciated.
Sean
- Original Message -
From: "John Raley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 03, 2001 12:20 PM
Subject: Re: Servlets, Beans, Str
rom: "Paul Tindall" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 03, 2001 3:37 PM
Subject: Re: Servlets, Beans, Struts, and Threading
> Sean,
>
> It is my undertanding that you do not want to do your own threading anywhere
> within a J2EE contain
ginal Message -----
> From: "John Raley" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, May 03, 2001 12:20 PM
> Subject: Re: Servlets, Beans, Struts, and Threading
>
> > Sean,
> >
> > You would probably not write the task as a Servlet
6 matches
Mail list logo
