[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

[ron_sigal]

anonymous wrote : 
  | Messaging uses whatever serialization Remoting Connector was configured with, both on client-to-server marshalling and vice-versa. We need to keep this consistent. Take a look at CallbackSErverFactory, for example, to see how this is configured. 
  |  

I was thinking of the following code from ServerPeer:


  |      // We explicitly associate the datatype "jms" with the java SerializationManager
  |       // This is vital for performance reasons.
  |       SerializationStreamFactory.setManagerClassName(
  |          "jms", "org.jboss.remoting.serialization.impl.jboss.JBossSerializationManager");
  | 
  |       JMSWireFormat wf = new JMSWireFormat();
  | 
  |       MarshalFactory.addMarshaller("jms", wf, wf);
  | 

I can't see a use of "jms" anywhere in Messaging, so I commented it out.

In any case, I updated JMSWireFormat with a constructor which takes an InvokerLocator parameter, from which it attemtps to get a serializationType value.  If there is none, it defaults to "jboss".  All JMSWireFormat instances in Messaging 1.0 are now created with a call to this new constructor, with the exception of one test case, which should be happy with the defaults (transport = "socket", serializationType = "jboss").

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973373#3973373

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973373