WSDL generation issue for the same webservice deployment
Sgc Manorite
Greenhorn
Joined: Jun 05, 2008
Posts: 12
posted
0
I have deployed a web service and I am using Axis jars (axis1.4.jar, axis2-kernel-1.3.jar, axis-ant.jar). The WSDL generated (after I click in the WSDL link) next to the web service name has some discrepancies from the WSDL generated before.
WSDL snippet of the old WSDL...
<wsdl:message name="getUserDetailsRequest"> <wsdl :p art name="credential type="tns1:Credential"/> <wsdl :p art name="userDetailsCriteria" type="tns3:userDetailsCriteria"/> </wsdl:message> <wsdl:message name="userDetailsResponse"> <wsdl :p art name="getUserDetailsReturn" type="tns3:userDetailsResponse"/> </wsdl:message>
WSDL snippet of the new WSDL... <wsdl:message name="getUserDetailsRequest"> <wsdl :p art name="in0" type="tns1:Credential"/> <wsdl :p art name="in1" type="tns3:userDetailsCriteria"/> </wsdl:message> <wsdl:message name="userDetailsResponse"> <wsdl :p art name="getUserDetailsReturn" type="tns3:userDetailsResponse"/> </wsdl:message>
Notice the change in the "part name" of the old and new WSDls. There has been no change in the WSDD. Doe to this the old clients which I had created using the old WSDL does not work. Could anybody please commnet on why this happens and the fix? Thanks in advance. [ November 06, 2008: Message edited by: SGC Manorite ]
Jimmy Clark
Ranch Hand
Joined: Apr 16, 2008
Posts: 2187
posted
0
Doe to this the old clients which I had created using the old WSDL does not work.
Could you reword this sentence? It does not make any sense.
Thanks.
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.
subject: WSDL generation issue for the same webservice deployment
0
peration name="getUserDetails" parameterOrder="in0 in1">
