So far, we don't send start/stop events. You could go a different way and declare a reference of type WebModule (the JSR-77 GBean representing the web module) and then your GBean would get a Collection containing all the web module GBeans, and I think you can register listeners to be notified as entries are added and removed. The GBeans would be added as the module is started and removed when the module is stopped.
As for the module ID default/foo-webapp/1150467344244/war, that's of the form group/artifact/version/type. So it looks like either you deployed this web app without a module ID or specified only the artifactId in your moduleId -- "default" is the default group, "foo-webapp" is either the name of your WAR or the artifactId you specified, 1150467344244 was the timestamp at the time of deployment, which is used if as the version if no version is specified. With this there are various ways to navigate to more interesting things, but the WebModule might be a better way to start. Thanks, Aaron On 6/16/06, Stefan Arentz <[EMAIL PROTECTED]> wrote:
On 6/16/06, Aaron Mulder <[EMAIL PROTECTED]> wrote: > In 1.1, your GBean just needs to implement DeploymentWatcher (from the > kernel module) and declare that in its list of interfaces. Hmm. Good hint, but it only solves halve of my puzzle :-) The DeploymentWatcher is only called when a web app is deployed/undeployed. I would also like to listen to start/stop events. Is that defined in the app server or is it web container specific? Also, is there an easy way to get more specific information about an artifact? When I print the web app's artifact is looks like this: default/foo-webapp/1150467344244/war. Is the 1150467344244 some unique id that I can lookup somewhere? S.
