[ http://jira.codehaus.org/browse/XFIRE-653?page=all ]
Dan Diephouse closed XFIRE-653.
-------------------------------
Resolution: Won't Fix
<int></int> is invalid XML according to the XML schema. You can either specify
that the number is nillable and do <int xsi:nil="true"> or specify minOccurs=0
and leave the element out of the message completely. So I'm marking this as
won't fix. Let us know if you have any other issues.
> Allow empty elements for schema types: int long double float
> ------------------------------------------------------------
>
> Key: XFIRE-653
> URL: http://jira.codehaus.org/browse/XFIRE-653
> Project: XFire
> Issue Type: Bug
> Components: Aegis Module
> Affects Versions: 1.2.1
> Environment: JDK 1.5
> XFire 1.2.1
> Reporter: Per Salomonsson
> Assigned To: Dan Diephouse
> Attachments: patch.txt
>
>
> Allow empty elements for schema types: int long double float
> consider the "someidentifier" to be of type int (schema standard) in a soap
> request towards a XFire service, this will fail in xfire with a
> NumberFormatException:
> .....
> <someidentifier></someidentifier>
> ...
> This patch allows this behaviour and inserts a '0' from the class
> org.codehaus.xfire.aegis.AbstractMessageReader instead of throwing a
> NumberFormatException.
> I'm not really sure what is really correct WSDL/SOAP-wise, but atleast XFire
> will be more compatible with other 3pp's!
> In this case: Oracle SOA Suite
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
