[
https://issues.apache.org/jira/browse/AXISCPP-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526395
]
fehrin edited comment on AXISCPP-716 at 9/11/07 5:25 AM:
------------------------------------------------------------------
I nailed down the issue with the current solution to the following:
1) There is a base type containing attributes.
2) There is an extension type based on the base type above containing
attributes on its own.
Then the attributes from the base type get lost during code generation, i.e.
the set of extension type attributes replaces the set of base type attributes
instead of augmenting the base type attributes with its own attributes.
This is not directly related with the attributes being optional or not.
This should be easy to fix, if one knows the exact code snippet.
The issue described here is a regression with respect to previous behaviour,
code was generated for both sets of attributes until the latest fix.
was (Author: fehrin):
I nailed down the issue with the current solution to the following:
1) There is a base type containing attributes.
2) There is an extension type based on the base type above containing
attributes on its own.
Then the attributes from the base type get lost during code generation, i.e.
the set of extension type attributes replaces the set of base type attributes
instead of augmenting the base type attributes with its own attributes.
This is not directly related with the attributes being optional or not.
This should be easy to fix, if one knows the exact code snippet.
> 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
> Assignee: 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]
