cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Commented: (CXF-2608) Typedefinition is not reflected in the SOAP-request
Date Fri, 08 Jan 2010 17:37:03 GMT


Daniel Kulp commented on CXF-2608:

I'm failing to see anything wrong.  

There is not a "CustomerOrderItemValue" type defined anywhere.    The only thing similar defined
is "JrCustomerOrderItemValue".   Since the list of items is defined as:
 			<xs:element name="item" type="jrom-v2-0:JrCustomerOrderItemValue" minOccurs="0" maxOccurs="unbounded"/>
and there are no subclasses or anything of JrCustomerOrderItemValue, there isn't a need for
any xsi:type on the "item" element.   The type is properly and fully defined from the schema.

> Typedefinition is not reflected in the SOAP-request
> ---------------------------------------------------
>                 Key: CXF-2608
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.2.5
>         Environment: 1.6.0_15
>            Reporter: Knut Ivar Skogland
>         Attachments:
> I have a problem when invoking a webservice with SOAP. I use CXF to generate code from
a wsdl, but the service does not validate this;
>    <ns1:customerOrderItems>
>       <ns1:item>
>               <ns2:action>actionFTW!!</ns2:action>
>       </ns1:item>
>    <ns1:customerOrderItems>
> The problem is the "item" tag. The server does not want the "item" object here, but wants
an object that extends item; "CustomerOrderItemValue" (yes, the wsdl states that this type
extends item).
> However.., this works:
>    <ns1:customerOrderItems>
>       <ns1:item xsi:type="ns1:CustomerOrderItemValue">
>               <ns2:action>actionFTW!!</ns2:action>
>       </ns1:item>
>    <ns1:customerOrderItems>
> This was originally posted to the CXF users mailinglist, but I've made a small testproject
containing the wsdl and sample code.
> The project should build with maven. Mock the service with the wsdl (resources/wsdl/test/)
and alter the url in the main method.
> One soaprequest is stored in the request.xml (incase you want to se the request without
mocking and running the application).
> Note that the wsdl and all the XSD's are not "my doing" ..., but is from another system
that I have to integrate with... lucky me. :)

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

View raw message