[
https://issues.apache.org/jira/browse/AXIS2-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902960#action_12902960
]
David J. M. Karlsen commented on AXIS2-4534:
--------------------------------------------
I don't see any relation to AXIS-2945 I however have an slightly different
usecase.
Given a type someType with an attribute someAttribute where the someType is
nillable.
If the element of someType is nil and has an someAttribute value of xyz the
attribute won't be retrievable as the the element being the parent is null.
> A non nillable element can be provided with an empty tag and thus resulting
> in null pointer errors
> --------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4534
> URL: https://issues.apache.org/jira/browse/AXIS2-4534
> Project: Axis2
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.4
> Environment: Linux, Java 1.5 (I think), Axis2-1.4
> Reporter: Carsten Sierks
> Priority: Minor
>
> In a complex element our wsdl states:
> <xs:element maxOccurs="1" minOccurs="1" name="Content"
> type="xs:base64Binary"/>
> i.e. the element is not nillable.
> For some reason the user of the service provided it with an empty tag, i.e.
> <Content/>.
> The result was, that in the method within the skeleton the Content parameter
> was preset with null, which was not taken into account by the logic.
> I would have expected the deserialisation to throw an error to the service
> user that an empty tag is not alloved.
--
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]
