Hi Chris,
That is what I understood of it.
But looking at Anne's reponse, it sounds like the difference between
'wrapped' and 'normal' is whether all your parameters get send or not.
If "document" means you're sending one document, not several parameters,
then why does it allow you to set multiple parts in the WSDL? Why not
put this constraint on the number of parts and call it doc/lit instead
of having one doc/lit style that does not work, and one doc/lit
'wrapped' style that does.
There must be more to this. I think I'll have to spend some time
googling and reading books this weekend..
Thanks,
Dies
Ebert, Chris wrote:
I use 'wrapped' style pretty much exclusively. The difference to me is
the XML that goes across the wire has an element that wraps the
parameters that I can use in my server to distinguish the operation
requested. It also makes Schema validation a little clearer: it couples
the set of parameters with the operation in the XML so the validation
covers both.
Hope that helps.
Chris
-----Original Message-----
From: Dies Koper [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 19, 2006 17:23
To: [email protected]
Subject: Re: Java2WSDL
Hello Anne,
I think I still do not quite understand the consequences of the
different styles.
Looking only at document style, I understood there is wrapped and
unwrapped (bare?).
With wrapped you have to have at most 1 part in your soap:operation.
So I understood this as you can have multiple parts with unwrapped.
Yet, when you use multiple parts, only the first one is serialized. Is
that what unwrapped is and why everybody advices not to use it? Because
you can define the parts, but they won't get send anyway? Or are there
any usecases where this is desireble?
As I understand, I do not quite get it yet..
Thanks,
Dies
Anne Thomas Manes wrote:
It is not a bug. Document style does not support parameters -- it
takes a document in and returns a document. If you would like to use
an RPC programming style with document/literal, then you must use the
WRAPPED style. Axis will then automatically generate a wrapping
document-style element for your parameters.
Anne
On 1/19/06, Dies Koper <[EMAIL PROTECTED]> wrote:
Hello Nicolas,
I have noticed the same, I think it is a bug.
Use document/literal(WRAPPED) instead of document/literal when you
create your WSDL (-y WRAPPED, IIRC). That should work.
Regards,
Dies
Nicolas De Loof wrote:
I'd like to use Java2Wsdl to build a WSDL for my business service
Business method is "public boolean isSiteDroit(String idSiu, String
idDroit)"
It works fine in "rpc" mode, but in document mode, Java2WSDL creates
this WSDL message :
<wsdl:message name="isSiteDroitRequest">
<wsdl:part element="impl:idSiu" name="idSiu"/>
<wsdl:part element="impl:idDroit1" name="idDroit"/>
</wsdl:message>
When I generate an axis client using WSDL2Java The SOAP message
contains in its body two elements <soap:body>
<idSiu>x</idSiu>
<idDroit1>1</idDroit1>
</soap:body>
The business method is invoked, but receives null as second argument.
When running debugger in axis code, I've found only the first soap
parameter is read and used for method invocation.
Is this expected ? How to build my wsdl to work ?
Nico.
--
Dies KOPER <[EMAIL PROTECTED]> (changed on 1 July 2005) Fujitsu Ltd
- MWPF1 (changed from MWPF3 on 21 Nov 2005) 2-15-16, Shin-Yokohama,
Kouhoku-ku, Yokohama, 222-0033, Japan Tel. +81(45)-475-5605 (internal
7181-4217)
--
Dies KOPER <[EMAIL PROTECTED]> (changed on 1 July 2005) Fujitsu Ltd -
MWPF1 (changed from MWPF3 on 21 Nov 2005) 2-15-16, Shin-Yokohama,
Kouhoku-ku, Yokohama, 222-0033, Japan Tel. +81(45)-475-5605 (internal
7181-4217)
--
Dies KOPER <[EMAIL PROTECTED]> (changed on 1 July 2005)
Fujitsu Ltd - MWPF1 (changed from MWPF3 on 21 Nov 2005)
2-15-16, Shin-Yokohama, Kouhoku-ku, Yokohama, 222-0033, Japan
Tel. +81(45)-475-5605 (internal 7181-4217)
