We have a requirement do let a client call services on our server using XML messages. We think SOAP fits this bill. However , we have problems persuading the cusomter to use HTTP. Is it too much of an overhead to use SOAP over RMI? Are they meant to be a similar thing?
This isn't the main point of my question. If we decided that we were going to use SOAP over RMI, we need a good way to access SOAP on the server side. ie bypassing the servlet. I have looked at the source code for the servlet. It does a lot of stuff HTTP dependant. I have also looked at RPCRouter.java. This seems to be what I need to call SOAP from a stateless session EJB for example. However I think I could give Envelope.unmarshall an XML SOAP document, but from what I can see this is far away from what I need to do. I suspect the SOAP services will still be administered using the servlet. The issue I think I will have will be classloaders in WLS 6.1. ie the WAR file where SOAP will be, would be in a child classloader of the EJB (in the same EAR). Therefore any servicemanager objects or any singletons may exist more than once. Will this be a problem? Has anybody got any example code to go from a SOAP request XML document, to a calling a SOAP service (living in the same process), but administered by the web app? I hope this makes a little bit fo sense ;-) Any help appreciated Paul ____________________________________________________________ Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie
