[jboss-jira] [JBoss JIRA] Commented: (JBREM-675) Problems with Servlet invoker
[ http://jira.jboss.com/jira/browse/JBREM-675?page=comments#action_12385458 ]
Ron Sigal commented on JBREM-675:
---------------------------------
The default exception handling behavior is now to return the exception thrown by the
invocation handler. To turn off that behavior, so that an error message is returned, it
is necessary to add the parameter
org.jboss.remoting.transport.http.HTTPMetadataConstants.DONT_RETURN_EXCEPTION (actual
value "dont-return-exception") with a value of "true" to the metadata
map received by ServerServletInvoker. For example, "dont-return-exception=true"
could be added to the InvokerLocator.
This change is related to JBREM-813 "ServletServerInvoker should return an exception
instead of just an error message".
Problems with Servlet invoker
-----------------------------
Key: JBREM-675
URL: http://jira.jboss.com/jira/browse/JBREM-675
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Attachments: ServletServerInvoker.java
Several problems with servlet invoker:
1) There can't be two servlet invokers (it's necessary, for example, if you want
to use them for JBoss Messagning and for EJBs - they require separate connectors) because
ObjectName is hard-coded in ServletServerInvoker.java
2) Null returns from invokers are sent to client as empty 204 responses and custom
marshallers have no change to process return value. This breaks JBoss Messaging which
expects that EVERY message contains at least two bytes (version tag and format tag).
--
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