[jboss-dev-forums] [Design of POJO Server] - Re: Getting the whole cause stack of the deployment exceptio

alesj do-not-reply at jboss.com
Thu Aug 6 06:57:22 EDT 2009


"pete.muir at jboss.org" wrote : 
  | Also, it would be useful to have the name of the MC bean which threw the exception (as we get in contextsInError) - this allows me to discard all non WB related exceptions.
  | 
MC bean name == ControllerContext::getName ;-)
Where ControllerContext is a parameter here:

  |  void handleException(T exception, ControllerContext context);
  | 

"pete.muir at jboss.org" wrote : 
  | So, what is the best way to attach an exception handler?
  | 
Simple define a WBNotificationListener in some -jboss-beans.xml
and it will be automagically picked up by MC and added to DeployersImpl.

"pete.muir at jboss.org" wrote : 
  | Can we add something to the PS API for this?
  | 
No.
And that's not what Adrian and me are saying PS should do.
OK, it already has this DeploymentManager, but this looks like it doesn't expose enough.
It should be the ManagedDeployment that should be able to give you the right exception, no matter how wrapped it is.

Or if MD is not the right place, something else should. Scott, Emanuel?


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248426#4248426

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248426



More information about the jboss-dev-forums mailing list