"adinn" wrote : | I suspect WS needs the unmarshaller to be called in both cases even when the stream is null i.e. we may need to back out this fix. Ho wsensible this is as regards any other remoting clients I am not in a position to say. Perhaps you could comment? | Well, logically, I think it doesn't make sense to call an unmarshaller with a null InputStream. Having fixed what I think should be considered a bug, I think rolling back the fix would amount to building in special treatment for a particular case (SOAP unmarshaller). On the other hand, by eliminating a call to the unmarshaller, I have changed the behavior of Remoting in an SP release, something I try to avoid. So I think I'll reopen the case and add a parameter, say "unmarshalnullstream", such that HttpClientInvoker defaults to the original behavior which can be changed to the new behavior by setting "unmarshalnullstream=true". If you use the SOAP unmarshaller in both (one way / two way) cases, then I assume this change would fix your problem. I was going to release a version 2.5.0.SP1 today, but I'll hold off briefly while we resolve this problem. I'll attach another jboss-remoting.jar to JBREM-1046. "adinn" wrote : | Sorry, for the previous misdiagnosis | I'd say it was a partial diagnosis, treated with a partial cure, rather than a misdiagnosis. Anyway, np, it's all good. -Ron View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184979#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...