Hi Thomas,
The servlet spec doesn't require the servlet container maintains the
servlets active all the time. Each vendor can implement that or not the way
it finds better. It doesn't seem you need a servlet for that...if you're
listening several different ports (not through the container) it seems more
adequate to work in a common network oriented java class (sort of Java-based
server). Probably you don't use HTTP to communicate through those different
ports ?
Wellington
-----Original Message-----
From: Thomas Eitzenberger
[mailto:[EMAIL PROTECTED]]
Sent: 07 December 2000 14:30
To: [EMAIL PROTECTED]
Subject: How to design a application context servlet
Hi all !
We are at the moment designing a telecom focused portal here
at Siemens
Austria based on EJB technology. Due to the restrictions of
EJB we are
not able to cover port listeners inside the EJBs and are
thinking of
"outsourcing" this task to a JSP/Servlet engine.
For this to work we would need a servlet that is started in
the startup
of the Servlet engine and will stay in memory (so not
serialized/passivated) and active all the time. It will
create a pool of
threads that will listen on different ports for incoming
messages from
external systems and will forward this info via JMS to the
EJB container.
Now according to my fellows here the Servlet Spec 2.2 does
NOT cover any
"application scope" servlet. In other words it is NOT
guaranteed that a
servlet is active al the time Is this right ?? Is there no
way to get a
servlet to be in memory and active all the time the servlet
engine is
running ?
Please respond to mailto:[EMAIL PROTECTED]
Any help would be greatly appreciated
with best regards and happy tomcatting :o)
ET
