Any chance you could check with the 2.0.4 release candidates available at: http://people.apache.org/~dkulp/stage_cxf/2.0.4-incubator/
There were definite issues with Exceptions not working correctly with qualified schemas in 2.0.3. They should (hopefully) be fixed there. Dan On Thursday 24 January 2008, Marco Piraccini wrote: > I need to expose a service (java-first) with CXF with an exception > (EchoComplexException > ) that includes an array of object (of class EchoStruct). > The service is setted with: anonymousWrapperType, qualifyWrapperSchema > ad wrapped to true. > > The wsdl generated seems to be correct, with a wrapper > EchoComplexException of the type: > > <xs:complexType final="#all" name="echoStructArray"> > <xs:sequence> > <xs:element maxOccurs="unbounded" minOccurs="0" name="item" > nillable="true" type="tns:echoStruct"/> > </xs:sequence> > </xs:complexType> > > The problem is that, on object deserialization, the > EchoComplexException is serialized in: > > <EchoComplexException xmlns="xxx"> > <ns2:reason xsi:type="echoStructArray" xmlns="yyy" xmlns:ns2="xxx" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > <item xmlns="" xmlns:ns4="yyy"> > <ns4:fieldBoolean>true</ns4:fieldBoolean> > </item> > </ns2:reason> > </EchoComplexException> > > ...that's correct, except for the xmlns="" item namespace. Of course > the schema validation fails. > > Anyone meet the same problem? > > Marco. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
