cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bricout (JIRA)" <>
Subject [jira] Created: (CXF-151) Element ref not supported in message types definitions
Date Fri, 13 Oct 2006 11:38:35 GMT
Element ref not supported in message types definitions

                 Key: CXF-151
             Project: CeltiXfire
          Issue Type: Bug
    Affects Versions: 2.0-M1
            Reporter: Michael Bricout

Example: wsdl + schema snippets


  <wsdl:message name="SetResourcePropertiesRequest">
    <wsdl:part name="SetResourcePropertiesRequest"
               element="wsrf-rp:SetResourceProperties" />


  <xsd:element name="SetResourceProperties">
      <xsd:choice minOccurs="1" maxOccurs="unbounded">
        <xsd:element ref="wsrf-rp:Insert" />
        <xsd:element ref="wsrf-rp:Update" />
        <xsd:element ref="wsrf-rp:Delete" />


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:
For more information on JIRA, see:


View raw message