[
http://jira.jboss.com/jira/browse/JBREM-544?page=comments#action_12339674 ]
Tom Elrod commented on JBREM-544:
----------------------------------
Test cases:
org.jboss.test.remoting.transport.http.HTTPInvokerTestCase
org.jboss.test.remoting.transport.servlet.ssl.SSLServletInvokerTestClient
org.jboss.test.remoting.transport.servlet.ServletInvokerTestClient
Note:
org.jboss.test.remoting.transport.web.WebInvokerTestClient.makeExceptionInvocation() is
where can see the two different configurations for handling server errors.
http client invoker (for http, https, servlet, and sslservlet) needs
to handle exceptions in same manner as other transport implementations
-------------------------------------------------------------------------------------------------------------------------------------------
Key: JBREM-544
URL:
http://jira.jboss.com/jira/browse/JBREM-544
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: general
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.CR1 (Boon)
All the other transport clients will throw an exception from the Client.invoke() method
when an error occurs. However, the http client invoker currently does not. This is a
problem in that can not deliver on no api changes when changing transports. However,
there is a need (by the web services group) to have the exception NOT thrown. So need to
provide option for both behaviors.
--
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