[
https://issues.apache.org/jira/browse/AXIS2-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5750.
------------------------------------
Resolution: Fixed
Assignee: Andreas Veithen
Fix Version/s: 1.7.2
> Fixed value causes Exception for non fixed values in ADB generated code
> -----------------------------------------------------------------------
>
> Key: AXIS2-5750
> URL: https://issues.apache.org/jira/browse/AXIS2-5750
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.6.4, 1.7.1
> Reporter: Frederik Hansen
> Assignee: Andreas Veithen
> Fix For: 1.7.2
>
> Attachments: FixedValueSample.wsdl, fixedAttribute.patch,
> fixedValue.patch, fixedValue.patch, fixedValue.patch
>
>
> I'm using Axis 1.7.1 and found an issue using fixed values in WDSL and the
> ADB Codegenerator.
> Basically when one fixed value/attribute exists, all attributes are treated
> as fixed attributes. This means, when setting the value on a non-fixed
> attribute, it set be seen as null (but set) and causing an exception once
> used to send to server.
> I've attached a simplified WSDL.
> I've looked in the ADB Codegen code, and IMHO the issue seems to be in
> SchemaCompiler where the code says:
> // register the fixed value if present
> if (xsElt.getFixedValue() != null) {
> metainf.registerDefaultValue(xsElt.getQName(),
> xsElt.getFixedValue());
> metainf.setFixed(true);
> }
> The setFixed seems to be too broad, and maybe it can be changed into
> something following the registerNillableQName-flow, e.g.
> registerFixedQName(xsElt.getQName()).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
