Axis2 Webservice model

[Former Member]

Hi Guys,

I've got a third party WSDL which has references to Axis2 framework. I'm trying to create a model using this WSDL. But it doesn't do anything. The model is not getting created.

If I create a standalone Java Client using Axis jars, the standalone Java Client gets created successfully, and works fine.

Is it possible to force NWDS to use Axis jars to create the model? Or is there a workaround to this situation?

Thanking in anticipation.

Regards,

-Vaibhav.

The WSDL is as follows:

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:axis2="http://test.sap.com/traceanalysis/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:ns0="http://traceanalysis.dto.test.sap.com/xsd" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:ns1="http://test.sap.com/traceanalysis/xsd/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://test.sap.com/traceanalysis/">
  <wsdl:documentation>Test service</wsdl:documentation> 
<wsdl:types>
<xs:schema xmlns:ax22="http://traceanalysis.dto.test.sap.com/xsd" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://traceanalysis.dto.test.sap.com/xsd">
  <xs:element name="TraceResultCollection" type="ax22:TraceResultCollection" /> 
<xs:complexType name="TraceResultCollection">
<xs:sequence>
  <xs:element name="logistics" nillable="true" type="ax22:Logistics" /> 
  <xs:element name="production" nillable="true" type="ax22:Production" /> 
  </xs:sequence>
  </xs:complexType>
  <xs:element name="Logistics" type="ax22:Logistics" /> 
<xs:complexType name="Logistics">
<xs:sequence>
  <xs:element maxOccurs="unbounded" name="movement" nillable="true" type="ax22:Movement" /> 
  </xs:sequence>
  </xs:complexType>
  <xs:element name="Movement" type="ax22:Movement" /> 
<xs:complexType name="Movement">
<xs:sequence>
  <xs:element name="customerNo" nillable="true" type="xs:string" /> 
  <xs:element name="scanDate" nillable="true" type="xs:string" /> 
  <xs:element name="shipmentNo" nillable="true" type="xs:string" /> 
  </xs:sequence>
  </xs:complexType>
  <xs:element name="Production" type="ax22:Production" /> 
<xs:complexType name="Production">
<xs:sequence>
  <xs:element name="batchNo" nillable="true" type="xs:string" /> 
  <xs:element name="palletCode" nillable="true" type="xs:string" /> 
  <xs:element name="productionDate" nillable="true" type="xs:string" /> 
  <xs:element name="shipperCode" nillable="true" type="xs:string" /> 
  </xs:sequence>
  </xs:complexType>
  </xs:schema>
<xs:schema xmlns:ns="http://test.sap.com/traceanalysis/xsd/" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://test.sap.com/traceanalysis/xsd/">
<xs:element name="getTraceResultsFault">
<xs:complexType>
<xs:sequence>
  <xs:element name="getTraceResultsFault" type="xs:anyType" /> 
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:element name="getTraceResults">
<xs:complexType>
<xs:sequence>
  <xs:element name="product" nillable="true" type="xs:string" /> 
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:element name="getTraceResultsResponse">
<xs:complexType>
<xs:sequence>
  <xs:element name="return" nillable="true" type="ns0:TraceResultCollection" /> 
  </xs:sequence>
  </xs:complexType>
  </xs:element>
  </xs:schema>
  </wsdl:types>
<wsdl:message name="getTraceResultsMessage">
  <wsdl:part name="part1" element="ns1:getTraceResults" /> 
  </wsdl:message>
<wsdl:message name="getTraceResultsResponse">
  <wsdl:part name="part1" element="ns1:getTraceResultsResponse" /> 
  </wsdl:message>
<wsdl:message name="getTraceResultsFault">
  <wsdl:part name="part1" element="ns1:getTraceResultsFault" /> 
  </wsdl:message>
<wsdl:portType name="TraceAnalysisServicePortType">
<wsdl:operation name="getTraceResults">
  <wsdl:input xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" message="axis2:getTraceResultsMessage" wsaw:Action="urn:getTraceResults" /> 
  <wsdl:output message="axis2:getTraceResultsResponse" /> 
  <wsdl:fault message="axis2:getTraceResultsFault" name="getTraceResultsFault" /> 
  </wsdl:operation>
  </wsdl:portType>
<wsdl:binding name="TraceAnalysisServiceSOAP11Binding" type="axis2:TraceAnalysisServicePortType">
  <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /> 
<wsdl:operation name="getTraceResults">
  <soap:operation soapAction="urn:getTraceResults" style="document" /> 
<wsdl:input>
  <soap:body use="literal" /> 
  </wsdl:input>
<wsdl:output>
  <soap:body use="literal" /> 
  </wsdl:output>
<wsdl:fault name="getTraceResultsFault">
  <soap:body use="literal" /> 
  </wsdl:fault>
  </wsdl:operation>
  </wsdl:binding>
<wsdl:binding name="TraceAnalysisServiceSOAP12Binding" type="axis2:TraceAnalysisServicePortType">
  <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /> 
<wsdl:operation name="getTraceResults">
  <soap12:operation soapAction="urn:getTraceResults" style="document" /> 
<wsdl:input>
  <soap12:body use="literal" /> 
  </wsdl:input>
<wsdl:output>
  <soap12:body use="literal" /> 
  </wsdl:output>
<wsdl:fault name="getTraceResultsFault">
  <soap12:fault use="literal" name="getTraceResultsFault" /> 
  </wsdl:fault>
  </wsdl:operation>
  </wsdl:binding>
<wsdl:binding name="TraceAnalysisServiceHttpBinding" type="axis2:TraceAnalysisServicePortType">
  <http:binding verb="POST" /> 
<wsdl:operation name="getTraceResults">
  <http:operation location="getTraceResults" /> 
<wsdl:input>
  <mime:content type="text/xml" /> 
  </wsdl:input>
<wsdl:output>
  <mime:content type="text/xml" /> 
  </wsdl:output>
  </wsdl:operation>
  </wsdl:binding>
<wsdl:service name="TraceAnalysisService">
<wsdl:port name="TraceAnalysisServiceSOAP11port_http" binding="axis2:TraceAnalysisServiceSOAP11Binding">
  <soap:address location="http://localhost:8080/proj1/services/TraceAnalysisService" /> 
  </wsdl:port>
<wsdl:port name="TraceAnalysisServiceSOAP12port_http" binding="axis2:TraceAnalysisServiceSOAP12Binding">
  <soap12:address location="http://localhost:8080/proj1/services/TraceAnalysisService" /> 
  </wsdl:port>
<wsdl:port name="TraceAnalysisServiceHttpport1" binding="axis2:TraceAnalysisServiceHttpBinding">
  <http:address location="http://localhost:8080/proj1/rest/TraceAnalysisService" /> 
  </wsdl:port>
  </wsdl:service>
  </wsdl:definitions>

[Former Member]

Hi vaibhav,

If you think that you need to add jars to your WD project simply add the Axis jars from Add External jars tab

It will be better if you post what error you are getting

Regards

Smruti

[Former Member]

Thanks for the reply guys.

Sumit, which file exactly you are referring to in the .metadata folder? I can't see any log file, I can see some backup, properties, etc. files.

Smruti, When I create a model, it simply doesn't do anything. I can't see a model created. However I can see some relevant files created, when I switch to Navigator view. In WebDynpro DC it is not possible to add the external jars in the build path. We create a external library DC and use that in WebDynpro DC. I've done that. But it doesn't work.

That's the reason, I've given the WSDL. So if someone is able to create a model or directly call the Web Service methods or create a deployable proxy, please let me know.

Regards,

-Vaibhav.

[Former Member]

Hi vaibhav,

What's the error u r getting while creating the model??If its not showing anything ,check the log file in ur workspace.it will be available in .metadata folder in ur workspace.

regards

Sumit

[former_member185029]

Hello Vaibhav,

1. If you check your WSDL, the server name is refered as localhost. Replace it with actual server name

2. Test your WSDL with XML Spy.

Ashu

[Former Member]

Ashutosh,

I think localhost issue will come into picture when the model is created succesfully. I'm not able to create model in first place. As mentioned it works fine with a standalone java client. What will be the advantage of testing with XML Spy?

Regards,

-Vaibhav.

[former_member185029]

XML Spy gives you idea if your WSDL is valid and can a request be sent over it.

Testing in stand alone java and importing model are 2 different things my frnd.

If you pretty sure it is not the problem then plz ignore my sugession

Ashu