On 09/06/2011 18:44, Calum wrote:
> On 9 June 2011 09:11, Pid wrote:
>> Eh? Why would you need to put Tomcat specific dependencies in a spec
>> compliant Servlet container? The above is simply not true.
>>
>> The OP use of a ServletContextListener is perfectly valid, (even if the
>> rest of the
On 9 June 2011 09:11, Pid wrote:
> Eh? Why would you need to put Tomcat specific dependencies in a spec
> compliant Servlet container? The above is simply not true.
>
> The OP use of a ServletContextListener is perfectly valid, (even if the
> rest of the code is a little odd).
Is it better to h
On 07/06/2011 16:33, Bill Miller wrote:
> If you want to work with threads in tomcat you need to know about the Tomcat
> org.apache.catalina.LifecycleListener interface.
Eh? Why would you need to put Tomcat specific dependencies in a spec
compliant Servlet container? The above is simply not true
yes, did that and it's working now. when contextDestroyed is called, i set the
bool to false and force the loop out. What i was missing is loop is exited when
> if ((inputLine = in.readLine()) != null)
this is completed, so, from Server class what i did is
Listener.requestStop(); // this cause
If you want to work with threads in tomcat you need to know about the Tomcat
org.apache.catalina.LifecycleListener interface. If you implement the interface
and register your
class within server.xml your class will be notified of Tomcat life cycle events
(Start, Stop,
etc...). You can then do app
