Werner:
I was wrong in my first mail. Actually it is no body block that I created. I
created something like this:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope>
<SOAP-ENV:Body>
<ns1:myMethod>
<args .../>
</ns1:myMethod>
<Insurance>
<bla...>
</Insurance>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
So it is one body-block with several entries inside of it. It was confusing
me because the method that accesses these entries is called
SOAPEnvelope.getBodyByName()
best regards
Matthias Wimmer
-----Original Message-----
From: Dittmann Werner [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 24, 2002 3:29 AM
To: '[EMAIL PROTECTED]'
Subject: AW: Several SOAP body blocks - can Axis deal with it
Hi Mathias,
do you really have two SOAP body blocks in the SOAP
envelope??? As I read the spec there is only _one_
real SOAP body allowed in an SOAP envelope. The same
is true for Header. However, the Body as well as
the Header may contain several so called blocks (body
or header blocks).
For RPC one of the body blocks
contains the struct that forms the RPC. My question
was: can a real SOAP body, when using for RPC, contain
an additional body block that contains another XML
structurce that is independent of the RPC.
As I read the spec this is allowed. The spec states:
<quote>
- An RPC invocation is modelled as a struct
- The invocation is viewed as a single struct containing
an accessor for each in or in/out parameter. The struct
is both named ean typed identically to the procedure
or method name
</qute>
IMO this does not restrict the number of body blocks
in a real SOAP body. Or do I understand the wording/meaning
wrong?
Regards
Werner
> -----Urspr�ngliche Nachricht-----
> Von: Wimmer, Matthias [mailto:[EMAIL PROTECTED]]
> Gesendet: Freitag, 21. Juni 2002 20:17
> An: '[EMAIL PROTECTED]'
> Betreff: RE: Several SOAP body blocks - can Axis deal with it
>
>
> 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
>
