[
https://issues.apache.org/jira/browse/AXISCPP-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-607.
------------------------------
Resolution: Fixed
This particular issue relating to elements has been resolved by AXISCPP-894.
> Nested namespace prefixes
> -------------------------
>
> Key: AXISCPP-607
> URL: https://issues.apache.org/jira/browse/AXISCPP-607
> Project: Axis-C++
> Issue Type: Bug
> Components: Serialization
> Reporter: Mark Whitlock
>
> Copied from a note to the mailing list.....
> The enumeration test sends this request message...
> <SOAP-ENV:Body>
> <ns1:getInput xmlns:ns1="http://enumeration.test.apache.org";>
> <type att_enum_int="1" att_enum_string="one"
> att_enum_kind="CHEQUE">
> <ns1:enum_int>0</ns1:enum_int>
> <ns1:enum_string>one</ns1:enum_string>
> </type>
> </ns1:getInput>
> </SOAP-ENV:Body>
> but when run against the latest WebSphere Application Server, the server
> returns a deserialization fault. The problem seems to be prefixing enum_int
> and enum_string. When these elements are unqualified (the prefixes are
> removed), it works. The wsdl does not specify elementFormDefault, and the
> default value is elementFormDefault="unqualified".
> I discovered http://www.w3.org/TR/xmlschema-0/ which explains this. It says
> in section 3.1 2nd para "Qualification of local elements and attributes can
> be globally specified by a pair of attributes, elementFormDefault and
> attributeFormDefault, on the schema element, or can be specified separately
> for each local declaration using the form attribute. All such attributes'
> values may each be set to unqualified or qualified, to indicate whether or
> not locally declared elements and attributes must be unqualified. ". From
> this and the other examples they give, elementFormDefault="unqualified" means
> that an instance document (basically a soap message) must not qualify
> elements within a complex type.
> So it seems that this is a bug in Axis C++. There are other schema attributes
> which we probably don't support properly such as form, fixed, ref, use and
> attributeFormDefault.
> What do other people think? Have I interpreted the specs correctly? Do other
> people use elementFormDefault? If I fix it, will it break the server?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
