You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Jerry DuVal (JIRA)" <ax...@ws.apache.org> on 2005/11/30 03:52:30 UTC
[jira] Created: (AXIS-2321) Add new property to allow nillable priority over minOccurs="0" when both are on the smae element and nillable="true"
Add new property to allow nillable priority over minOccurs="0" when both are on the smae element and nillable="true"
---------------------------------------------------------------------------------------------------------------------
Key: AXIS-2321
URL: http://issues.apache.org/jira/browse/AXIS-2321
Project: Apache Axis
Type: New Feature
Components: Serialization/Deserialization
Versions: 1.3
Reporter: Jerry DuVal
Priority: Trivial
Losing placeholder when nillable="true" and minOccurs="0" attributes on the same element
>>>
>>> Original Request
I'm having a issue related to using nillable="true" and minOccurs="0" attributes on the same element. When setting these elements to null the placeholder for the element with xsi:nil="true" is only being sent when the element does not have the minOccurs="0" . I have a example included below to display both the packet sent from axis and the same packet sent using PHP 5.0 distributed SOAP. Why does axis not sent the place holder for promiseDate since it has the nillable="true" and the element was set to null? Is this a bug?
//WSDL for updateJob service
<xsd:complexType name="Job">
<xsd:sequence>
<xsd:element name="promiseDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
<xsd:element name="dateSetup" nillable="true" type="xsd:dateTime"/>
</xsd:sequence>
</xsd:complexType>
//Java code for setting attributes for the service
job.setPromiseDate( null );
job.setDateSetup( null );
//Packet sent to Web Service
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<updateJob xmlns="urn://pace2020.com/epace/sdk/UpdateObject">
<job>
<ns15:dateSetup xsi:nil="true" xmlns:ns15="http://pace2020.com/epace/object"/>
</job>
</updateJob>
</soapenv:Body>
</soapenv:Envelope>
//PHP 5.0 distributed SOAP lib
// code for setting attributes for the service
$existingJob -> promiseDate = null;
$existingJob -> dateSetup = null;
//Packet sent to Web Service
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<updateJob xmlns="urn://pace2020.com/epace/sdk/UpdateObject">
<job>
<ns15:promiseDate xsi:nil="true" xmlns:ns15="http://pace2020.com/epace/object"/>
<ns15:dateSetup xsi:nil="true" xmlns:ns15="http://pace2020.com/epace/object"/>
</job>
</updateJob>
</soapenv:Body>
</soapenv:Envelope>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-2321) Add new property to allow nillable priority over minOccurs="0" when both are on the smae element and nillable="true"
Posted by "Jerry DuVal (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2321?page=all ]
Jerry DuVal updated AXIS-2321:
------------------------------
Attachment: diff.zip
> Add new property to allow nillable priority over minOccurs="0" when both are on the smae element and nillable="true"
> --------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS-2321
> URL: http://issues.apache.org/jira/browse/AXIS-2321
> Project: Apache Axis
> Type: New Feature
> Components: Serialization/Deserialization
> Versions: 1.3
> Reporter: Jerry DuVal
> Priority: Trivial
> Attachments: diff.zip
>
> Losing placeholder when nillable="true" and minOccurs="0" attributes on the same element
> >>>
> >>> Original Request
> I'm having a issue related to using nillable="true" and minOccurs="0" attributes on the same element. When setting these elements to null the placeholder for the element with xsi:nil="true" is only being sent when the element does not have the minOccurs="0" . I have a example included below to display both the packet sent from axis and the same packet sent using PHP 5.0 distributed SOAP. Why does axis not sent the place holder for promiseDate since it has the nillable="true" and the element was set to null? Is this a bug?
>
> //WSDL for updateJob service
> <xsd:complexType name="Job">
> <xsd:sequence>
> <xsd:element name="promiseDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
> <xsd:element name="dateSetup" nillable="true" type="xsd:dateTime"/>
> </xsd:sequence>
> </xsd:complexType>
> //Java code for setting attributes for the service
> job.setPromiseDate( null );
> job.setDateSetup( null );
> //Packet sent to Web Service
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <updateJob xmlns="urn://pace2020.com/epace/sdk/UpdateObject">
> <job>
> <ns15:dateSetup xsi:nil="true" xmlns:ns15="http://pace2020.com/epace/object"/>
> </job>
> </updateJob>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
> //PHP 5.0 distributed SOAP lib
> // code for setting attributes for the service
> $existingJob -> promiseDate = null;
> $existingJob -> dateSetup = null;
>
> //Packet sent to Web Service
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <updateJob xmlns="urn://pace2020.com/epace/sdk/UpdateObject">
> <job>
> <ns15:promiseDate xsi:nil="true" xmlns:ns15="http://pace2020.com/epace/object"/>
> <ns15:dateSetup xsi:nil="true" xmlns:ns15="http://pace2020.com/epace/object"/>
> </job>
> </updateJob>
> </soapenv:Body>
> </soapenv:Envelope>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira