[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-813) ServletServerInvoker should return an exception instead of just an error message

Ron Sigal (JIRA) jira-events at lists.jboss.org
Sun May 25 02:42:42 EDT 2008


    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12414155 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

The default behavior described above applies only to the 2.2 branch.  In the 2.x branch (for release 2.4), the default behavior is to throw an exception.  The original behavior of returning an error message can  be requested by setting the parameter HTTPMetadataConstants.DONT_RETURN_EXCEPTION (actual value "dont-return-exception") to "true".

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        



More information about the jboss-remoting-issues mailing list