axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5750) Fixed value causes Exception for non fixed values in ADB generated code
Date Tue, 22 Mar 2016 19:53:25 GMT


Andreas Veithen commented on AXIS2-5750:

The unit test is actually not testing the code generated by ADB, but the code generated by

> Fixed value causes Exception for non fixed values in ADB generated code
> -----------------------------------------------------------------------
>                 Key: AXIS2-5750
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen
>    Affects Versions: 1.6.4, 1.7.1
>            Reporter: Frederik Hansen
>         Attachments: FixedValueSample.wsdl, fixedAttribute.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.
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message