David Jencks wrote: > > I don't exactly remember, but I think there was a reason the event > fires > before. It may hae had something to do with the farm deployer.
Yes the comment next to the notification mentioned the farm service. Although I would think (in my ignorance) that the farm service wouldn't want to farm out a deployment unless it succeeded on the original machine, would it? > How does your mbean fit in the packaging? Is there some way you can > use the > jboss service lifecyle to get the same effect? I'd think that it > might be > difficult to guarantee that your mbean was ready to recieve > notifications > even if the notifications occurred after the deployment was done. > I can wait for the DeploymentScanner to "finish starting" through MBean dependencies, yes. Then when my MBean start()s I can get a list of all deployments and extract what I need for each one. This would cover all production use of our app and most development use, and would probably be enough. So this is what I will go with, thanks. But, that doesn't cope with redeployments. It's a shame that there's no safe way to 'listen' to deployment events inside the MBeanServer - I'm sure people could do lots of interesting things if they did. Chris ------------------------------------------------------- This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
