"alesj" wrote : "pete.muir(a)jboss.org" wrote :
| | This should be checked when we're unwinding the exception to its cause,
| | as you never know who all is wrapping the real cause.
| Yes, this is probably enough control for those who need to dig deeper into deployment
exceptions, especially if I can get the whole stack here.
| "alesj" wrote : Wrt to having entire exception in IDE, I think we would need
to change too much code, in order to still properly display any useful info.
| | (we're already not the greatest there, but the issue is more complex than it
| For me, IDE isn't a big problem. My use case is that I need to examine deployment
exceptions (root cause and sometimes the next level or so up) in an testsuite so I can
verify that the correct error happened on deployment.
| But, I can see that this is more generally applicable in the area of tooling (both
prod via Jopr, and dev via JBoss Tools) - that if an accurate deployment exception(s) can
be reported back to the tool, it can start to suggest possible remedies...
View the original post :
Reply to the post :