A SOAP stack does more than just convert messages to objects. A SOAP message consists of a SOAP Header and a SOAP Body. A SOAP stack must process all entries in the SOAP Header before processing the SOAP Body. Then, when processing the SOAP Body, it can pass the XML payload to an application or it can convert the XML payload into Java objects and invoke an appropriate method. Also, the SOAP stack processes faults -- it converts Java exceptions into SOAP Faults.
SOAP messages are always XML; they are never HTML. Most SOAP stacks provide a POJO framework. Services typically don't need to know anything about the framework. But ... you need to deploy your POJOs into the SOAP framework. It's a bit more challenging if you want to deploy your POJOs into a different framework, although not impossible. In any case, Apache SOAP is a very antiquated SOAP stack. No serious updates have been made to it since early 2002. This project has been superceded by Apache Axis (see http://ws.apache.org/axis). Axis gives you a lot more flexibility, and it supports all the latest and greatest SOAP features. Axis also gives you the ability to define your own dispatch provider, so you should be able to adapt it to work with your framework. Anne On 8/22/05, Dean Hiller <[EMAIL PROTECTED]> wrote: > I am looking for a soap stack. What I mean by this is I am looking for > something that converts the soap messages(html/xml) to objects and > objects back to soap messages. I am not looking for a framework that > routes my messages. I currently have a pojo framework where services no > nothing about the platform. I would like to keep it that way, and would > like to add soap, and rmi so services can be accessed via those methods. > thanks, > dean > > >
