Hi Anne, Referring to "The "RPC" provider maps XML to Java objects. It supports any style of message (document/literal, rpc/literal, and rpc/encoded). And depending on your settings, it can map the XML message to a single object, or it can automatically "unwrap" a message and map the children of the message to beans or types."
Does it work with doc/literal as well? On 1/10/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
Pedro, It's important to distinguish between the Axis WSDD "style" and the WSDL "style". The Axis WSDD styles represent a combination of WSDL styles and programming styles. The WSDL styles include document/literal, rpc/literal, and rpc/encoded. These styles represent the way messages are encoded. Note that the WSDL style is orthogonal to the way the application interfaces with the Axis framework. The programming styles represent the way applications interface with the framework. The programming style that you use corresponds to the "provider" that you use to send and receive messages. The "MSG" provider maps XML to DOM. The MSG provider only supports document/literal style messages. The "RPC" provider maps XML to Java objects. It supports any style of message (document/literal, rpc/literal, and rpc/encoded). And depending on your settings, it can map the XML message to a single object, or it can automatically "unwrap" a message and map the children of the message to beans or types. The WSDD styles correspond to providers, programming styles, and WSDL styles this way: Message: MSG provider / map XML messages to DOM / document/literal Document: RPC provider / map XML message to a single value object / document/literal Wrapped: RPC provider / map XML child elements to beans or types / document/literal RPC + use="literal": RPC provider /map XML parameters to beans or types / rpc/literal RPC: RPC provider / map XML parameters to beans or types /rpc/encoded Given that your application works at the XML/DOM level, then you want to stick with "message" style. Anne On 1/8/07, Pedro Silveira Vieira da Silva <[EMAIL PROTECTED]> wrote: > Hi, > > Although it might be strange to be asking this after developing an > application with Axis, the truth is that there are some questions still > open. > > I've developed an application that makes use of axis for creating a web > service for XML message exchanging. More accurately I have a service > that receives a XML document with some information and makes some > processing with it, rebuilds it and sends it back to the server for some > other job. > > For this implementation I've chosen the Message service style, but I've > been wondering why not use the Document style since I'm exchanging > documents? I know that the document style has a return type of void, > which by itself would explain why not use it for message exchanging (at > least I think ...). But since Message style seems to be an axis specific > implementation, is there any other way of doing this, even if it for > compatibility pour purpose? > > How was this done before Message style existed? > > Thanks in advance, > Pedro Silva > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- warm regards, Rahul Devgan Cell: +61-412163412 --- there is no pleasure in life like music ---
