• Post Reply Bookmark Topic Watch Topic
  • New Topic

copied wsdl from url to file won't work  RSS feed

 
john a wilson
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using wsdl2java from axis 1.4 to generate java classes (wsdl at bottom of message). The wsdl is at a remote location. However when I copy the wsdl into a file and attempt to generate the classes of that I am getting all sorts of namespace errors. Can anyone tell me why apparently the same wsdl from a URL is OK but won't work when copied locally (the reason I want to do this is that the stub from the remote wsdl is not creating the desired message).

Thanks for any help,

john

Also my understanding is that the wsdl below is document literal style (wrapped). It is wrapped because the name of the operation (process) is also the name of element for the input message. Is this correct?

wsdl (note that I have replaced any sensitive information with elipses):

<wsdl:definitions targetNamespace=".....">
<!--WSDL created by Apache Axis version: 1.3 Built on Oct 05, 2005 (05:23:37 EDT)-->
<wsdl:types>
<schema targetNamespace="....">
<import namespace="...."/>
<element name="process" type="xsd:anyType"/>
</schema>
<schema targetNamespace="....">
<element name="processReturn" type="xsd:anyType"/>
<element name="fault" type="xsd:anyType"/>
</schema>
</wsdl:types>
<wsdl:message name="processResponse">
<wsdl:part element="impl:processReturn" name="processReturn"/>
</wsdl:message>
<wsdl:message name="processRequest">
<wsdl:part element="tns1:process" name="part"/>
</wsdl:message>
<wsdl:message name="WebServicesRuntimeException">
<wsdl:part element="impl:fault" name="fault"/>
</wsdl:message>
<wsdl:portType name="WebServiceExceptionLoggingAdapter">
<wsdl:operation name="process">
<wsdl:input message="impl:processRequest" name="processRequest"/>
<wsdl:output message="impl:processResponse" name="processResponse"/>
<wsdl:fault message="impl:WebServicesRuntimeException" name="WebServicesRuntimeException"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="...." type="impl:WebServiceExceptionLoggingAdapter">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="process">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="processRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="processResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="WebServicesRuntimeException">
<wsdlsoap:fault name="WebServicesRuntimeException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="WebServiceExceptionLoggingAdapterService">
<wsdl:port binding="impl:..." name="....">
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

 
Yaron Naveh
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Maybe the original wsdl reference some other wsdl/xsd files which you didn't copy locally.
Check any <import /> <include /> elements.
 
john a wilson
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The original wsdl is exactly as in the first message (except for the ellipses) - at least this is what is displayed by my firefox browser - and surely firefox wouldn't be dropping stuff?

Its a remote wsdl so that is all I have access to
 
Ivan Krizsan
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi!
Have you tried one or more of the following:
1) Validated your local WSDL using Eclipse, NetBeans, Oxygen XML or some other tool?
2) Used your local copy of the WSDL as an input to soapUI, in order to generate some tests for the web service and then verify that the tests indeed pass?

Best wishes!
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!