What are the drawbacks of the solution wherein java objects are marshalled as byte arrays and sent as the body of the SOAP message? Is this a bad solution if you know that your client is Java based? I know all the traditional goals of WebServices being interoperable and all but if there are RMI limitations on scalability, then is this a good approach? Also, what are the drawbacks of such an implementation?

First how are you going to support deap copy, all the memory references will get screwed up. Second, JVM incompatibility etc should definately pop up somewhere. I mean the object instance was created by some JVM version, and is going to be used by some other JVM version. Definatly sounds trouble to me. Regards, Rakesh.