ReflectionMessageHandler - bug in creation of body elements?

[Jan Torben Heuer]

I have a problem with the ReflectionMessageHandler. (In other cases I wrote my 
own Handler, therefore I didn't find the problem before):

In this code:

    public Element toXML(Object result)
        throws SoapFault
    {
        Method method = getMethod();
        
        if (method == null)
            throw new IllegalStateException(_MESSAGES.get("NoMethod"));
        
        Class returnType = method.getReturnType();
        QName returnValueName = getReturnValueName();
        QName responseBodyName = getResponseName();
        
        //
        // void methods & no output part = no soap body
        //
        if (returnType == Void.TYPE && responseBodyName == null)
            return null;
        
        Element responseXML = XmlUtils.createElement(responseBodyName);

Muse generates the SOAP-Body from the WSDL description. In the last line it 
creates a new Element from the response name. Shouldn't this be rather the 
element type? Here is the concrete definition from our project's wsdl:

    <wsdl:message name="GetCapabilitiesResponse">
        <wsdl:part name="GetCapabilitiesResponse" element="ses:Capabilities"/>
    </wsdl:message>

In this case muse creates an element GetCapabilitesResponse although it should 
be ses:Capabilites.

So did we configure something wrong or is it a bug?


Jan


-- 
                                Institute for Geoinformatics
[EMAIL PROTECTED]       Robert-Koch-Strasse 26-28
+49 251 83-31960                48151 Münster, Germany

signature.asc
Description: This is a digitally signed message part.