1) If you create a WRAPPED style service, Axis will deserialize it into two arguments. If you create a DOCUMENT style service, Axis will deserialize it into a single object. If you create a MESSAGE style service, Axis will give you the SOAP body in XML.
2) If you would prefer to work with DOM, then you can use MESSAGE style, or you can use DOCUMENT style and deserialize it into a DOM element. Some people prefer to work with Java objects rather than with XML. The nice thing about Axis is that it supports both styles.
Anne
At 01:29 PM 8/18/2003 +0600, you wrote:
Hi all,
Consider a situation where there is a doc\literal web service which accepts two(or more) complex arguments.
1) Does axis engine deserialize it into two arguments?
2) Literal encoding means that the Body contents conform to a specific XML Schema, and that gives you lot of freedom. Isn't it more flexible if the axis engine deserialize the whole soapBody into a document?
Dimuthu.
