Hello, AXIS2-366 shows it was resolved but does not specify the version
it was fixed in. AXIS2-747 refers to using XLMBeans rather than ADB but
seems to be related to namespace prefix missing on child elements.
Listed below is what is the payload (in the SOAP body) using AXIS2. Note
the first <Header xmlns=" . . ." line. The service provider says the
namespace prefix should be referenced for the child elements and the
xmlns=" ..." in the <Header> should not be there. See Service Provider
example. The question is are these 2 requests functionally equivalent or
is there something wrong when using the elementFormdefault="qualified"
attribute with AXIS2?
AXIS 2 Request:
<ns2:ClaimNumberAssignmentRequest
xmlns:ns2="
http://www.companyX.com/us/ins/product/disability/custvendext";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:type
="ns2:ClaimNumberAssignmentRequest">
<Header xmlns="
http://www.companyX.com/us/ins/product/disability/custvendext/typelib";>
<SchemaVersion>10</SchemaVersion>
<Requestor>
<SourceID>aSourceID</SourceID>
<SourceReference>aSourceReference</SourceReference>
</Requestor>
<Operation>
<OperationMajor>OPMA</OperationMajor>
<OperationMinor>OPMI</OperationMinor>
</Operation>
</Header>
</ns2:ClaimNumberAssignmentRequest>
Service Provider example:
<ext:ClaimNumberAssignmentRequest
xmlns:ext="
http://www.companyX.com/us/ins/product/disability/custvendext";
xmlns:tl="
http://www.companyX.com/us/ins/product/disability/custvendext/typelib";>
<tl:Header>
<tl:SchemaVersion>1.0</tl:SchemaVersion>
<tl:Requestor>
<tl:SourceID>NBH</tl:SourceID>
<tl:SourceReference>RRRRT</tl:SourceReference>
</tl:Requestor>
<tl:Operation>
<tl:OperationMajor>5</tl:OperationMajor>
<tl:OperationMinor>6</tl:OperationMinor>
</tl:Operation>
</tl:Header>
<ext:ClaimNumberAssignmentRequest
"Amila Suriarachchi" <[EMAIL PROTECTED]>
10/08/2007 01:45 AM
Please respond to [email protected]
From
"Amila Suriarachchi" <[EMAIL PROTECTED]>
To
[email protected]
cc
Subject
Re: AXIS2 WSDL2Java (ADB) - XSDs with elementFormdefault=qualifed
On 10/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED] >
wrote:
Hello, it appears this problem had been reported before in apache.org/jira
but has gone unresolved. I currently have schemas that have this setting
specified but within the SOAP body the elements are missing the namepace
prefix.
could you please show us the jira number. or create a new jira with your
xsd file?
Does anyone know why this has not been fixed or if there is a version that
has it worked or has been fixed. It may just be broken in the more
recent versions. I have tried this in versions 1.2 and 1.3 with no luck.
Thanks ... Joe
--
Amila Suriarachchi,
WSO2 Inc.
