[jira] Created: (AXIS2-3175) Null arrays management is different when using hierarchies

["Jorge Fernández (JIRA)" <ji...@apache.org>]

Null arrays management is different when using hierarchies
----------------------------------------------------------

                 Key: AXIS2-3175
                 URL: https://issues.apache.org/jira/browse/AXIS2-3175
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: adb
    Affects Versions: 1.3
         Environment: Windows XP SP2, Tomcat 5.5, Java 1.5.0
            Reporter: Jorge Fernández
            Priority: Trivial


Hi,

I'm observing that when I have an object with array attributes, ADB
behaves different depending on whether that attribute is inherited or not.

If I have an inherited array, and I don't call its set method, that element
won't appear in the SOAP message. The client will see that the array is
null.

If in the same case, I set it to null, the element will appear as nil in
the SOAP message. The client sees an array of one null component.

With a non-inherited array, the element will appear as nil if I set it to
null and if I don't call the method too. The client sees an array of one
null component.

If I have an attribute that is not an array (ex: a String). Its behaviour
is the same if it's inherited or not. The element will appear as nil.

Why my client sees the array with one null component when the array comes
as nil?? Shouldn't see it as a null array??
Shouldn't it be better for a null attribute, not to appear in the message?

Thanks.

-- 
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