You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2006/10/25 10:43:18 UTC

[jira] Resolved: (CXF-151) Element ref not supported in message types definitions

     [ http://issues.apache.org/jira/browse/CXF-151?page=all ]

Freeman Fang resolved CXF-151.
------------------------------

    Resolution: Fixed

> Element ref not supported in message types definitions
> ------------------------------------------------------
>
>                 Key: CXF-151
>                 URL: http://issues.apache.org/jira/browse/CXF-151
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.0-M1
>            Reporter: Michael Bricout
>         Assigned To: Freeman Fang
>             Fix For: 2.0-M1
>
>
> Example: wsdl + schema snippets
> [wsdl]
>   <wsdl:message name="SetResourcePropertiesRequest">
>     <wsdl:part name="SetResourcePropertiesRequest"
>                element="wsrf-rp:SetResourceProperties" />
>   </wsdl:message>
> [schema]
>   <xsd:element name="SetResourceProperties">
>     <xsd:complexType>
>       <xsd:choice minOccurs="1" maxOccurs="unbounded">
>         <xsd:element ref="wsrf-rp:Insert" />
>         <xsd:element ref="wsrf-rp:Update" />
>         <xsd:element ref="wsrf-rp:Delete" />
>       </xsd:choice>
>     </xsd:complexType>
>   </xsd:element>
> Problem:
> This results into the following exception being thrown at service initialisation time:
>       java.lang.IllegalArgumentException: Invalid name [null]
>       in org.apache.cxf.service.model.AbstractMessageContainer.addMessagePart
> The issue can be further narrowed to this:
> In org.apache.cxf.wsdl11.WSDLServiceBuilder.isWrappableSequence(),
> we obtain the element's qualified name to be passed into AbstractMessageContainer.addMessagePart().
> el.getQName() returns null for the elements defined using "ref".
> It seems that getRefName() should instead be used in this case.
> The current workaround consists into replacing the element references with their actual types
> in the schema.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira