anonymous wrote :
| We changed the code off the remoting library for testing purposes to ensure
that exceptions are as well sent back as http 200 and get proper encoded (as in
the standard case). This works but I do not feel too comfortable with this
solution-
|
After further
this is now scheduled for the Remoting 2.4.0 release:
http://jira.jboss.com/jira/browse/JBREM-804
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4083794#4083794
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4083794
So far we didn't find a solution to set the property. They we understand the
documentation it is the proper remoting behaviour to use WebServerError if you
use servlet as transport (which we do). The appropriate http headers indicate
this as well as a 500 message.
This caused additional
We have the same problem using ejb3 over http with jboss-remoting coming along
with jboss4.2.0.
We also get the right exception when making calls over rmi but getting
UndeclaredThrowable caused WebServerError when making the same calls using http
as transport.
Any solutions to this? Is there
