[jira] Commented: (AXIS-2664) Axis generate invalid soap when using RPC/encoded where exists omittable fields (minOccurs=0) and nillable=false

["Marinó A. Jónsson (JIRA)" <ax...@ws.apache.org>]

    [ https://issues.apache.org/jira/browse/AXIS-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537566 ] 

Marinó A. Jónsson commented on AXIS-2664:
-----------------------------------------

I just hit this snag.  My first google hit was issue AXIS-2054, which really explains in detail my problem.  The "resolution" for that issue, however, is too superficial and doesn't work for me.

The key point Patrick makes here is that when a field _is not_ nillable but _is_ omittable it should indeed be omitted.

So - a compromise might look something like this:

// if meta data says minOccurs=0, then we should skip
// it if its value is null and either it's not nillable or we 
// aren't doing SOAP encoding.
if (isOmittable && (!isNillable || !isEncoded)) {
    continue;
}

> Axis generate invalid soap when using RPC/encoded where exists omittable fields (minOccurs=0) and nillable=false
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS-2664
>                 URL: https://issues.apache.org/jira/browse/AXIS-2664
>             Project: Axis
>          Issue Type: Bug
>          Components: Serialization/Deserialization
>    Affects Versions: 1.4
>            Reporter: Patrick Di Loreto
>
> While using axis 1.4 with webMethods EAI system I have encountered the following problem :
> Axis generate an invalid soap message in RPC/encoded WS where exists omittable (minOccurs="0") fields and nillable = "false".
> Axis don't omit the field when null but put it in soap message with nill value.
> Exploring source code I have found the following check in org.apache.axis.encoding.ser.BeanSerializer.java class at row : 222
>                             // if meta data says minOccurs=0, then we can skip
>                             // it if its value is null and we aren't doing SOAP
>                             // encoding.
>                             if (isOmittable && !isEncoded) {
>                                 continue;
>                             }
> It seams a choice to not apply omittable behavior while using soap/encoding. Is it correct ? Is it a standard ? WebMethods aspect that this field was omitted and not nill.
> I fixed it just as follow :
>                             // if meta data says minOccurs=0, then we can skip
>                             // it if its value is null and we aren't doing SOAP
>                             // encoding.
>                             if (isOmittable){ // && !isEncoded) {
>                                 continue;
>                             }
> What can I aspect on next version of Axis ? 
> Thx

-- 
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org