This week's book giveaway is in the Other Open Source APIs forum. We're giving away four copies of Storm Applied and have Sean Allen, Peter Pathirana & Matthew Jankowski on-line! See this thread for details.
Web Service is supposed to pass XML because of the interoperability issue. Because these byte codes/class files does some computation and are not simply messages, passing them as XML may not be work, right.
I am trying to use SOAP bindings here .... client sends these byte codes thru AXIS....AXIS takes the byte codes and serializes....deserialization on the server Web Service side...back to Java object....bindings still remains SOAP binding as on the client side.....but when I execute this on the server....fails ! Interestingly, these byte codes arrive safely on the server and when I run them on the server side via a command shell, works great !
This client code is similar to ones in their samples from Axis 1.1.
Best bet would be to use local binding because SOAP is expensive. In short, client sends class file on the server, server executes these arrived byte codes on the fly, the byte codes makes a local method call on the server Web Service already exposed methods, and comes back with the result. Hence, I consume less network resources.