cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From alexv <alexander.vaa...@exense.com>
Subject Re: [jira] Created: (CXF-1530) Nillable parameters not rendered.
Date Thu, 17 Apr 2008 08:01:36 GMT

What this problem boiles down to is that aegis in CXF does not honour the
minOccurs=1 on the parameters.
This is a wsdl snippet from the XFire service:
<xsd:element name="registrerKunde">
   <xsd:complexType>
     <xsd:sequence>
        <xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true"
type="ns1:InputDO"/>
        <xsd:element maxOccurs="1" minOccurs="1" name="in1" nillable="true"
type="ns2:CustomerDetailDO"/>
        <xsd:element maxOccurs="1" minOccurs="1" name="in2" nillable="true"
type="ns2:SomethingDO"/>
       <xsd:element maxOccurs="1" minOccurs="1" name="in3" nillable="true"
type="ns2:ArrayOfSomethingElseDO"/>
   </xsd:sequence>
  </xsd:complexType>
</xsd:element>

I have made a patch that hopefully fixes this problem and postet in in jira.

/Alex
  



Benson Margulies-4 wrote:
> 
> Let me make sure I'm following this. You have the same java code on both
> sides, and you are using Aegis on both sides. So we are all hoping that
> Aegis comes to the same conclusions in both the XFire and CXF versions.
> 
> As the person who made the most recent changes to Aegis, I am very
> pessimistic about this. I strongly recommend that you use wsdl2java to
> create a JAX-WS+JAXB client and use that, instead.
> 
> There is a lot of room for discrepancies to creep in to Aegis in
> comparison
> to XFire as we fix issues. I don't think that any of us have the
> wherewithall to come up with a testing methodology that would ensure that
> your scenario keeps working.
> 
> 

-- 
View this message in context: http://www.nabble.com/Re%3A--jira--Created%3A-%28CXF-1530%29-Nillable-parameters-not-rendered.-tp16721282p16740825.html
Sent from the cxf-dev mailing list archive at Nabble.com.


Mime
View raw message