[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-167) RMI Invoker does not use true remoting marshalling/unmarshalling

[Ron Sigal (JIRA)]

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

1. org.jboss.remoting.transport.rmi.RMIClientInvoker and RMIServerInvoker now have the ability to marshal and unmarshal in the server to client direction as well as the client to server direction.  

2. Marshalling in the client to server direction has been changed so that once an object has been marshalled into a ByteArrayOutputStream, it is not reread from an ObjectInputStream.  Instead, the byte array is passed directly to the proxy's transport() method.

3. Just in case, the original version of marshalling/unmarshalling is available by setting the new parameter RMIServerInvoker.RMI_ONEWAY_MARSHALLING (actual value "rmiOnewayMarshalling") to "true".  In fact, the original version has been fixed so that it works with JBossSerialization.

Unit tests:

org.jboss.test.remoting.transport.rmi.RMIInvokerTestCase has been split into

   * org.jboss.test.remoting.transport.rmi.RMIInvokerNativeMarshallerTestCase and
   * org.jboss.test.remoting.transport.rmi.RMIInvokerOnewayMarshallingTestCase

Also, two new tests have been added:

   * org.jboss.test.remoting.transport.rmi.RMIInvokerDecoratorTestCase and
   * org.jboss.test.remoting.transport.rmi.RMIInvokerOnewayMarshallingTestCase

Waiting for hudson results.

> RMI Invoker does not use true remoting marshalling/unmarshalling
> ----------------------------------------------------------------
>
>                 Key: JBREM-167
>                 URL: http://jira.jboss.com/jira/browse/JBREM-167
>             Project: JBoss Remoting
>          Issue Type: Bug
>          Components: transport
>    Affects Versions: 1.2.0 final
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>            Priority: Minor
>             Fix For: 2.4.0.CR1 (Pinto)
>
>
> In process of fixing JBREM-165 (RMI support for UnifiedInvoker), have added ability to call on mashaller when making request so that can modify payload before sending.  Although the RMIInvokerClient does use the configured marshaller, it does not use the configured unmarshaller (RMIInvokerServer is the opposite).  This was done to get JBREM-165 working, but is not a total solution and needs to be fixed so anyone can add a marshaller/unmarshaller for RMI invoker that will be called both ways (in and out) on both the client and server.  

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