[jbossws-issues] [JBoss JIRA] Updated: (JBWS-1704) The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All Requests

[Darran Lofthouse (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBWS-1704?page=all ]

Darran Lofthouse updated JBWS-1704:
-----------------------------------

    Component/s: jbossws-jaxrpc

> The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All Requests
> ----------------------------------------------------------------------------------------
>
>                 Key: JBWS-1704
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1704
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-jaxrpc
>    Affects Versions: jbossws-1.2.1
>            Reporter: Darran Lofthouse
>             Fix For: jbossws-2.1.0
>
>
> The use of JBoss Remoting causes a datatype parameter to be sent with all outgoing requests, this parameter is not required by the server and can cause problems as some loadbalancers reject the message.
> The reason for this is because of a workaround required in JBoss Remoting 1.4.5 to register the marshaller.  See the createRemotingClient method: -
> http://anonsvn.jboss.org/repos/jbossws/tags/jbossws-1.2.1.GA/jbossws-core/src/java/org/jboss/ws/core/client/RemotingConnectionImpl.java
> It is possible to check the Remoting version using the following method: -
>   public static int getDefaultVersion()
> From 'org.jboss.remoting.Version', a possible solution will be to check the version to decide if we need to register the marshaller in this way.

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