Nope I saying that if you want to know about your application being
deployed and undeployed or the container within which your application
is deployed being stopped and started you need to have a WAR.
A ServletContextListener is notified whenever the container deploys
(which also includes starts) and undeploys (which also includes stops)
the WAR within which the ServletContextListener is contained.
You then have that listener call your Stateless session bean or web
services that is in the EJB jar or whatever you have to say:
"Oy! we is starting" or "Oy! we is stopping"
Bung the whole lot in an EAR so that the start and stop do not run
into sequencing issues.
There are other ways of getting the start and stop events, but for
JavaEE version 5, this is the only _standards compliant_ way that I
know of.
On Tue, Jul 8, 2008 at 12:04 AM, <glassfish_at_javadesktop.org> wrote:
> So, are you saying that in order to get the WebService lifecycle methods to work (mind, this isn't a servlet listener, this is a simple WebService), that you need to have a WAR deployed?
>
> How are you deploying the web service. As a SessionBean, or as part of a web app?
>
> Are you suggesting, Stephen, that if I have a SessionBean web service deployed, that I still need minimal WAR in order to get the WebService lifecycle methods called on SessionBeans web services?
> [Message sent by forum member 'whartung' (whartung)]
>
> http://forums.java.net/jive/thread.jspa?messageID=284884
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>