cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grzegorz Grzybek (JIRA)" <>
Subject [jira] [Commented] (CXF-5254) Unmarshall exception if a sequence<string> is used in a struct.
Date Tue, 01 Oct 2013 08:25:24 GMT


Grzegorz Grzybek commented on CXF-5254:

One more thing. [CORBA to WSDL/SOAP Interworking (C2WSDL) spec|]
says in chapter " Sequences":

bq. XML Schema for WS-I conformant RPC/Literal Soap Binding – an IDL sequence is mapped
onto a sequence complex type (the SOAP encoding soapenc:Array type MUST NOT be used with WS-I
conformant soap bindings).

So I think that the sequences - even the ones contained in structs should have separate complex
type and the struct's member of type sequence should be separate element (in Juergen's case:
"s1") with the type of IDL sequence mapped to XSD complexType.

> Unmarshall exception if a sequence<string> is used in a struct.
> ---------------------------------------------------------------
>                 Key: CXF-5254
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: CORBA Binding
>    Affects Versions: 2.7.5, 2.7.6
>         Environment: JAVA7 / Windows 7
>            Reporter: Juergen Bockhorn
>            Priority: Blocker
>         Attachments:
> A server function returns a struct. This struct contains another struct which contains
a sequence<string>. Calling this method with a CXF/Corba-Client leads to an unmarshall
> {code}
> Warnung: Interceptor for {}repro.ServiceCORBAService#{}getFirst
has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: Unmarshalling Error: unerwartetes Element (URI:"",
lokal:"item"). Erwartete Elemente sind <{}id>,<{}s1>

> 	at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(
> 	at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(
> 	at
> 	at org.apache.cxf.interceptor.BareInInterceptor.handleMessage(
> ...
> {code}
> (sorry for german).
> Using a pure CORBA-client works.
> I will attach a repro project to this issue if I have figured out how it works :-)

This message was sent by Atlassian JIRA

View raw message