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

pete.muir@jboss.org do-not-reply at jboss.com
Thu Aug 6 06:45:32 EDT 2009


"alesj" wrote : Pete, can you check if JBDEPLOY-205 is actually useful for this issue (JBAS-7047)?

Yes, looks good, assuming I have a way to install one of these (as below). 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.

anonymous wrote : Otherwise, like Adrian said, we need to get this into ProfileService,
  | hence Scott or Emanuel are the one's that should help you with this.

I don't use ManagedDeployment at all. Instead I use http://anonsvn.jboss.org/repos/jbossas/projects/integration/trunk/jboss-profileservice-spi/src/main/java/org/jboss/deployers/spi/management/deploy/DeploymentManager.java and it's start/stop/distribute methods. Any deployment exceptions (IncompleteDeploymentException which I then dig into to get the underlying WB exception) are simply thrown out of these methods which we catch.

So, what is the best way to attach an exception handler? Can we add something to the PS API for this? Or should it be configured via -beans.xml or something?

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

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



More information about the jboss-dev-forums mailing list