"scott.stark(a)jboss.org" wrote : Ok, I have a test that shows the lack of the
underlying cause so I'm looking into how we can propagate that.
|
Most probably the ManagedDeployment API would fit better for this, as we have an
association between the deployment and failure. Although we could also propagate it to the
DeploymentProcess.
As using ManagedDeployments requires to initialize the ManagementView as well, which could
take while.
Basically we could catch the IncompleteDeploymentException in the DeployHandler as Adrian
mentioned and propagate the stacktrace(s) to the DeploymentID. There is a disconnect
though, as one DeploymentID can contain multiple names.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249647#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...