ron_sigal wrote : | 1. JMSWireFormat can't expect to get passed ObjectInputStreams and ObjectOutputStreams. This has been discussed already, although I can't find the reference. I changed it to create object streams as necessary. | timfox wrote : | BTW all the stream stuff in the marshaller is a big pain. | I have been having related issues since as you realised remoting always passes in a ObjectInput/Ouput Stream. | In TRUNK I have changed all this so that now the underlying stream is passed in, so you're changes in that area may not be necessary. | It looks to me that you both applied similar changes concurrently on TRUNK and Branch_1_0. Since we need to get CR5 out ASAP, how about Ron checks in his changes, and we will reconcile them with the trunk later? ron_sigal wrote : | oos = SerializationStreamFactory.getManagerInstance("key").createOutput(out); | "key" has to be replaced by a suitable value. I assume it would be acceptable to just hard code "jboss", [...] | 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. timfox wrote : | For JMS traffic (e.g. messages) going from server to client, how do you do this? (Obviously you can't have a HTTP server on the client accepting connections) | Do you poll the server from the client intermittently, or do you piggyback server to client traffic on return values of client to server traffic, or both? | Reiterating the same questions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973368#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...