Yes, exactly the Scanner works on a background thread so even if you do addURL() you
don't get immediate feedback.
Instead, I think I'll get the subdeployer notification that a module was either
started or destoyed, then I'll guery the main deployer for the DeploymentInfo object
that contains the reason, e.g.
| [EMAIL PROTECTED] {
url=file:/X:/cvs/jboss-public/jboss-4.0/build/output/jboss-4.0.1RC1/server/default/deploy/lolo-service.xml
}
| deployer: [EMAIL PROTECTED]
| status: Deployment FAILED reason: Trying to install an already registered mbean:
jboss.mq.destination:name=Z,service=Queue
| state: FAILED
| watch:
file:/X:/cvs/jboss-public/jboss-4.0/build/output/jboss-4.0.1RC1/server/default/deploy/lolo-service.xml
| altDD: null
| lastDeployed: 1098198222960
| lastModified: 1098198222950
| mbeans:
|
I might event call checkIncompleteDeployments() and see if I can figure-out something
from the exception.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3851917#3851917
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3851917
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
