Hi, I am working on a project where we would like to invoke both Stateful and Stateless EJBs via a web service with SOAP as the protocol.
We do not control the design of the EJBs and cannot influence such. Therefore the EJBs may return primitive, simple or complex objects. >From reading this list, it seems that when people have asked about complex and deep data structures the advice has been not to do it. It should be a case of writing (de)serializers for the complex types but again this seems to be advised against and there is no documentation for doing such. Another architectural alternative would be to provide our own Provider and use Apache SOAP for just the SOAP part; again there seems to be no documentation. Finally, the client to our system will not be Apache SOAP, nor MS - it will be a C SOAP implementation running on Solaris. Considering the intial problems between Apache and MS implementation would I be right to think that we could hit problems? >From what I have researched and read it would seem that although our project looks a cert for web services and SOAP, the implementations are not quite there in terms of being ready and useable in large projects today - is this fair? Regards Darren This message is intended only for the use of the person(s) (the "intended recipient (s)") to whom it is addressed. It may contain information which is privileged and confidential. If you are not the intended recipient, please contact the sender as soon as possible. The views expressed in this communication may not necessarily be the views of InterX plc. Any copyright in this message shall remain vested in InterX plc � and the intended recipient may only copy the same for internal business purposes or as otherwise stated in this message.
