[
https://issues.apache.org/jira/browse/AXIS2-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768179#action_12768179
]
Andreas Veithen commented on AXIS2-4534:
----------------------------------------
Carsten,
Please not that "I would have expected the deserialisation to throw an error to
the service user that an empty tag is not alloved." is incorrect. The empty
string is part of the value space of the xs:base64Binary type. Thus an empty
element is valid even if it has not been declared as nillable. However in that
case the service should not receive a null value, but an empty byte array or an
empty DataHandler.
> 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: Axis 2.0 (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.
