Any chance you can file a jira with a small test case?
My major concern is "why is it getting into the wrapper helpers at
all"? According to the JAXWS spec, the elements in the wrapper type
must NOT be nillable. If there are nillable=true flag there, it
cannot be considered unwrappable and thus must be code generated as
"bare". Thus, the wrapper helpers shouldn't be invoked at all.
Dan
On May 28, 2008, at 10:06 AM, nicolas de loof wrote:
My issue is related to the following declaration :
<element name="customerOrderUID" nillable="true" type="xsd:string"
minOccurs="0" maxOccurs="1"/>
As you can notice, the schema set nillable="true" AND minOccurs="0"
This schema has not been writen by XSD experts, and from MSDN
documentation
I can read that nillable implies the element is required.
Can you confirm this ?
I can't find the same rule from the XSL Schema spec at
http://www.w3.org/TR/xmlschema-1/. Do you have any link to describe
this XSD
rule ?
Nico.
2008/5/27 Benson Margulies <[EMAIL PROTECTED]>:
Could you try the 2.0.6 release? If it still don't work, please
make a
JIRA.
On Tue, May 27, 2008 at 10:44 AM, nicolas de loof
<[EMAIL PROTECTED]>
wrote:
Hello,
My WSDL types declares the "description" element with
minOccurs="0" :
<complexType name="DeliverLoyaltyAccountRequest">
<sequence>
<element name="description" nillable="false"
type="xsd:string"
minOccurs="0" maxOccurs="1"/>
...
When I invoke the service (using SoapUI) it works fine with
<sch:description></sch:description>
or <sch:description/>,
but when I *remove *this XML element, I get a NullPointerException :
Caused by: *java.lang.NullPointerException*
at
_33j
.services
.servicesmodification
.schema
.DeliverLoyaltyAccountRequest_WrapperTypeHelper1
.getWrapperParts(Unknown
Source)
at
org
.apache
.cxf.jaxws.interceptors.WrapperClassInInterceptor.handleMessage(*
WrapperClassInInterceptor.java:122*)
I'm using cxf 2.0.5-incubator
Did I miss something ?
---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog
