cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tawfik Lachheb (JIRA)" <>
Subject [jira] Created: (CXF-1251) Error from CXF if optional method argument is missing
Date Mon, 03 Dec 2007 19:46:43 GMT
Error from CXF if optional method argument is missing

                 Key: CXF-1251
             Project: CXF
          Issue Type: Bug
          Components: Aegis Databinding
            Reporter: Tawfik Lachheb
            Priority: Blocker
             Fix For: 2.1

Setting the minOccurs for method parameters in the aegis mapping file does not apply to the
wsdl so the wsdl shows method parameters like this for example (even with minOccurs set to
<xsd:element name="findLocation"> 
<xsd:element minOccurs="0" name="location" type="xsd:string"/> 
<xsd:element minOccurs="0" name="findOptions" type="tns:FindOptions"/> 
<xsd:element minOccurs="0" name="token" type="xsd:string"/> 

With minOccurs = 0, some toolkits would send the parameters like this if the findOptions parameter
is null: 

<soapenv:Envelope xmlns:soapenv="" xmlns:v20="">



Wich returns: 

<soap:Envelope xmlns:soap=""> 
         <faultstring>Current state not START_ELEMENT</faultstring> 

Not sure what the best way to fix it is but it seems like we either:
1- fix the code to apply the minOccurs from the aegis mapping files so clients don't send
this kind of request
2- fix the code to be able to handle the minOccurs of 0 on the server side

Please let me know if yo need any more info.


This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message