[jboss-jira] [JBoss JIRA] Commented: (JBREM-543) fix servlet invoker error handling to be more like that of the http invoker
[ http://jira.jboss.com/jira/browse/JBREM-543?page=comments#action_12339675 ]
Tom Elrod commented on JBREM-543:
----------------------------------
Have basically rolled back latest changes to allow for throwing of exceptions or be
configured to *not* throw an exception. Details can be found within JBREM-544.
Now servlet and http transports (and their children, https and sslservlet) behave the
same. Only difference in behavior will depend on if is calling on remoting server, where
original exception generated on server side will be thrown on the client or if is not
remoting server, will throw (or return if configured to not thow exception) a
WebServerError, who's message with the error html from the web server.
fix servlet invoker error handling to be more like that of the http
invoker
---------------------------------------------------------------------------
Key: JBREM-543
URL: http://jira.jboss.com/jira/browse/JBREM-543
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.CR1 (Boon)
Need to change the servlet invoker so on client side will not throw an exception out of
the Client's invoke() method call, but just return the error (as text in most cases)
and have the response code indicate the error status code (e.g. 500). Although this is
not exactly how the http invoker handles exceptions from the http server invoker, is only
way to reliably get errors from web containers (like Tomcat).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira