[jboss-jira] [JBoss JIRA] Created: (JBREM-804) Enable HTTPClientInvoker to accept NO_THROW_ON_ERROR configuration by way of InvokerLocator

[Ron Sigal (JIRA)]

Enable HTTPClientInvoker to accept NO_THROW_ON_ERROR configuration by way of InvokerLocator
-------------------------------------------------------------------------------------------

                 Key: JBREM-804
                 URL: http://jira.jboss.com/jira/browse/JBREM-804
             Project: JBoss Remoting
          Issue Type: Feature Request
      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)


Currently, the value for the parameter org.jboss.remoting.transport.http.HTTPMetadataConstants.NO_THROW_ON_ERROR in org.jboss.remoting.transport.http.HTTPClientInvoker is configurable only by  way of the invocation metadata map passed to org.jboss.remoting.Client.invoke().

However, for EJB3 invocations, the Client is created by the EJB3 proxy (org.jboss.aspects.remoting.InvokeRemoteInterceptor, in particular) and is not accessible by application code.  If HTTPClientInvoker checked the InvokerLocator for this parameter, then it could be configured declaratively in the EJB3 jboss-service.xml file.

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