RE: Axis2 interoperability with .Net

Lessard, Paul Tue, 14 Feb 2006 07:17:16 -0800

Anne,

I’m using 0.94 of Axis2, and I basically followed the first example on the User Guide. I just deployed out the axis2.war to my tomcat server, and posted a WebService in an aar file. The aar has the compiled code with 1 exposed method, and a services.xml in the META-INF subdir of the aar. Here is the services.xml:

This is a sample Web Service with two operations,echo and ping.

</description>

<parameter name="ServiceClass" locked="false">AdmitToDplWebService</parameter>

</operation>

</service>

The publicly exposed method is the following:

public OMElement admitToDpl(OMElement admitNumbers)

{

OMElement dplCodes = null;

try

{

dplCodes = setupReturnDocument();

Vector v = getDplCodes(admitNumbers);

addDplCodes(dplCodes, v);

}catch(Exception e)

{

System.err.println(“(admitToDpl): Could not retrieve a list of DPL codes for the passed in numbers. “+e);

}

Return dplCode;

}

The remaining code I don’t believe is relevant, but I can supply it if you need. The code does compile, and the web service works perfectly when using the axis2 EchoBlockingClient.java skeleton to access the web service. Is there any more information I can provide?

Thank you,

Paul Lessard

From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Monday, February 13, 2006 3:26 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 interoperability with .Net

What version of Axis2 are you using?
The generated WSDL has errors in it. All the schema attributes have been namespace qualified, but they should not be. e.g.,

<xs:element ns0:name="param0" ns1:type="xs:anyType" />

should be:

<xs:element name="param0" type="xs:anyType" />

Can you tell us what you did to generate the WSDL?

Anne

On 2/13/06, Lessard, Paul <[EMAIL PROTECTED]> wrote:

Hi all,

I'm trying to use the wsdl.exe prog provided by the .Net SDK and I'm getting some errors. Looking through past posts, this doesn't seem to be the "tn1" name problem that others had. The error I'm getting is the following:

Schema validation warning: The required attribute 'name' is missing.

Schema validation warning: For element declaration either the name or the ref attribute must be present.

Schema validation warning: The required attribute 'name' is missing.

Schema validation warning: For element declaration either the name or the ref attribute must be present.

Warning: Schema could not be validated. Class generation may fail or may produce incorrect results.

Error: Unable to import binding 'AdmitToDplBinding' from namespace 'http://org.apache.axis2/'.

- Unable to import operation 'admitToDpl'.

- The element 'http://org.apache.axis2/xsd:admitToDplRequest' is missing.

I'm just starting out in Web Services, so I'm not very familiar with WSDL files. Having said that, here is the auto-generated WSDL from Axis2 (sorry it isn't spaced out nicely):

<wsdl:definitions xmlns:ns1="http://org.apache.axis2/xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap=" http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://org.apache.axis2/" targetNamespace="http://org.apache.axis2/"><wsdl:types><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns2="http://www.w3.org/2001/XMLSchema" xmlns:ns0="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.w3.org/2001/XMLSchema" ns1:elementFormDefault="qualified" ns0:attributeFormDefault="unqualified" ns2:targetNamespace="http://org.apache.axis2/xsd">

<xs:element ns0:name="processDictaphoneRequest">

<xs:complexType>

<xs:sequence>

<xs:element ns0:name="param0" ns1:type="xs:anyType" />

</xs:sequence>

</xs:complexType>

</xs:element>

<xs:element ns0:name="processDictaphoneResponse">

<xs:complexType>

<xs:sequence>

<xs:element ns0:name="return" ns1:type="xs:anyType" />

</xs:sequence>

</xs:complexType>

</xs:element>

</xs:schema></wsdl:types><wsdl:message name="processDictaphoneResponseMessage"><wsdl:part name="part1" element="ns1:processDictaphoneResponse" /></wsdl:message><wsdl:message name="processDictaphoneRequestMessage"><wsdl:part name="part1" element="ns1:processDictaphoneRequest" /></wsdl:message><wsdl:portType name="DictaphonePort"><wsdl:operation name="processDictaphone"><wsdl:input message="tns:processDictaphoneRequestMessage" /><wsdl:output message="tns:processDictaphoneResponseMessage" /></wsdl:operation></wsdl:portType><wsdl:binding name="DictaphoneBinding" type="tns:DictaphonePort"><soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /><wsdl:operation name="processDictaphone"><soap:operation name="operation" soapAction="processDictaphone" style="document" /><wsdl:input><soap:body use="literal" namespace="http://www.org.apache.axis2" /></wsdl:input><wsdl:output><soap:body use="literal" namespace="http://www.org.apache.axis2" /></wsdl:output></wsdl:operation></wsdl:binding><wsdl:service name="Dictaphone"><wsdl:port name="DictaphonePortType" binding="tns:DictaphoneBinding"><soap:address location="http://fh2k039.fhmis.net:8080/axis2/services/Dictaphone" /></wsdl:port></wsdl:service></wsdl:definitions>

Anybody have any ideas? It's probably something blindingly obvious, but as said, I'm quite new to Web Services.

Thank you,

Paul Lessard

RE: Axis2 interoperability with .Net

Reply via email to