[
https://issues.apache.org/jira/browse/AXISCPP-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495535
]
Franz Fehringer commented on AXISCPP-716:
-----------------------------------------
There seems to be a flaw in the optional attributes solution implemented with
AXISCPP-716.
It shows up under the following circumstances::
* There is a base type containing optional attributes.
* From this base type another type is derived via extension.
Then *no* code is generated for the optional attributes contained in the
derived type.
More to the point: For the optional attributes implicitely contained in the
derived type (via extension from the base type) no code is generated.
> Support for the attribute construct 'use'
> -----------------------------------------
>
> Key: AXISCPP-716
> URL: https://issues.apache.org/jira/browse/AXISCPP-716
> Project: Axis-C++
> Issue Type: Improvement
> Components: Client - Deserialization, Serialization, Server -
> Deserialization, SOAP, WSDL processing - Doc, WSDL processing - RPC
> Affects Versions: current (nightly)
> Reporter: Adrian Dick
> Assigned To: nadir amra
> Fix For: current (nightly)
>
>
> Currently, there is no support for the 'use' construct on attributes defined
> in a WSDL file.
> The values this can take are:
> - required
> - optional
> - prohibited
> The current default behaviour we provide matches to 'required', although
> WSDL2Ws does not validate this is definitely the case.
> To support optional we would need to do something similar to the behaviour
> for nillable on elements.
--
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]
