"tfennelly" wrote : We're just talking about the embedded http gateway here re breaking backward compatibility, right? Making this work for the HttpRouter, JBR Gateway etc will mean using the "in addition" approach talked about by Dave, with the data potentially ref'd by the message from multiple places, right?
The only area we discussed in the meeting was the http gateway, which we already know is going, and my previous comment was definitely directed at that provider.
If this extends into the others then we need to discuss it further. Perhaps I misunderstood the question from earlier.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240915#4240915
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240915
"pete.muir(a)jboss.org" wrote : Perhaps the ability to install a custom exception handler which get's notified on a context in error?
Yup, this doesn't sound bad.
I guess we can match an exact exception type or any that's in its sub class hierarchy.
This should be checked when we're unwinding the exception to its cause,
as you never know who all is wrapping the real cause.
We can probably also do a match on the MC contexts that are roots of the problem.
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 looks like)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240868#4240868
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240868