input name in the wsdl generated from cxf 2.1* doesn't have "Request"

[liw]

Hi,

We are migrating from xfire to cxf. We noticed that the input name in the
wsdl generated from cxf is different from the one generated from xfire.

For example, with xfire we have 

 <wsdl:portType name="LocationService">
        <wsdl:operation name="getAccountLocation">
            <wsdl:input message="tns:getAccountLocationRequest"
name="getAccountLocationRequest"/>
            <wsdl:output message="tns:getAccountLocationResponse"
name="getAccountLocationResponse"/>
            <wsdl:fault message="tns:ApiFault" name="ApiFault"/>
        </wsdl:operation>
    </wsdl:portType>


However, with cxf, the input name is "getAccountLocation" instead of
"getAccountLocationRequest".

<wsdl:portType name="LocationService">
        <wsdl:operation name="getAccountLocation">
            <wsdl:input message="tns:getAccountLocation"
name="getAccountLocation"/>
            <wsdl:output message="tns:getAccountLocationResponse"
name="getAccountLocationResponse"/>
            <wsdl:fault message="tns:ApiFault" name="ApiFault"/>
        </wsdl:operation>
    </wsdl:portType>


I wonder if there is any specific reason to introduce this difference in
cxf. Does anyone know how the difference impacts the existing web service
clients who uses the old wsdls?

My understanding is that input name is just used to reference the message
definition in the wsdl document. It's something internal to the wsdl and not
exposed to any soap client tool such as SoapUI and Axis. However, I didn't
find any info about how the input name is used in the wsdl 1.1 spec. 

Please let me know if you have any thoughts on this.

Thanks in advance,

Li



 


  
-- 
View this message in context: 
http://www.nabble.com/input-name-in-the-wsdl-generated-from-cxf-2.1*-doesn%27t-have-%22Request%22-tp25144464p25144464.html
Sent from the cxf-user mailing list archive at Nabble.com.