I just scanned through the WS-I Basic Profile, and I found no rules or recommendations to specify "unqualified". It does indication that the child element of the <soap:Body> should be qualified, and it states that the child elements of <soap:Fault> must be unqualified, but I see no recommendation for elementFormDefault="unqualified". IMO, such a recommendation would be inappropriate. I view it as a schema design decision.
In any case, my recommendation is that Axis2 should always generate the elementFormDefault attribute -- whether it's qualified or unqualified.
Anne
On 5/19/06,
Kinichiro Inoguchi <[EMAIL PROTECTED]> wrote:
Hi,
I'm testing to call Axis2 service from .NET client.
When I used Axis2 0.95, I could do that,
but after upgrade to Axis2 1.0, I can't.
.NET client can sends request message to Axis2
service,
and Axis2 service receives that and sends response
message to .NET client.
I saw actual in/out XML messages with TCPMon 1.0.
Though, .NET client got 'Nothing' object as response.
But, I changed 'elementFormDefault' of WSDL schema to
'qualified', and re-generated .NET proxy code,
.NET client got response successfully !!
It seems elementFormDefault="qualified" was default
generated WSDL settings at 0.95.
With 1.0 elementFormDefault="unqualified" seems
default.
I saw WS-I recommend "unqualified",
so I'd like to verify "unqualified", too.
Does anyone succeed interop test between Axis2 1.0
and .NET with WSDL elementFormDefault="unqualified" ?
Thanks,
kinichiro
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
