Hi all, I have to implement a Web service that processes some transmitted data. The data has to be in XML format.
This is what I did: I wrote a Web service, that is invoked by RPC. The transmitted data is added as a second body to the SOAP envelope. I implemented it in Axis and it works fine. But now I am a little confused by your communication. Is this way actually not the accurate way to achieve this goal? There are two other possibilities: Possibility 1: Move the whole XML-data into this RPC-body. (The place where usually the arguments are.) Possibility 2: Not to use this RPC stuff at all. Only send the XML-data and the server invokes the correct method anyway. But I have to admit that I have absolutely no idea about all this stuff. Is there any tutorial what one is able to do if he doesn't want to use RPC? I appreciate every opinion to this. Matthias Wimmer -----Original Message----- From: Dittmann Werner [mailto:[EMAIL PROTECTED]] Sent: Friday, June 21, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: Several SOAP body blocks - can Axis deal with it Hi all, according to the SOAP specs <quote> The (SOAP Body) element MAY contain a set of SOAP body blocks, each being an immediate child element of the SOAP Body. </quote> Axis (in RPC and/or doc/lit mode) processes (at least?) one immediate child element. What happens if there are more immediate child elements? Does Axis filters the child elements and uses only those relevant for its processing? (Silently ignoring the other child elements?) The other immediate child elements would be processed by e.g. a customized handler. Some documentation available about this topic or some link into the source where I can check? Regards, Werner Werner Dittmann Siemens ICM N PG ES AS TP mailto:[EMAIL PROTECTED] Tel: +49(0)89 722 42481/+49(0)172 85 85 245
