Re: Problem in interoperability between .net web services and axis2 stub client
seems to be a problem with the response message. Look at the response message using tcpmon[1] thanks, Amila. [1]http://ws.apache.org/commons/tcpmon/ On Fri, Dec 26, 2008 at 1:10 PM, Aseem Sharma aseem_bat...@yahoo.co.inwrote: Hello All, I am getting following error upon calling web services developed in .net through client stub devloped in axis2 1.4 (xmlbeans binding, asynchronous). I am getting this error in my callback handler. org.apache.axis2.AxisFault: An error occurred on the server. at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416) at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:441) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Unknown Source) Please help me to resolve this problem. Thanks, Aseem sharma -- View this message in context: http://www.nabble.com/Problem-in-interoperability-between-.net-web-services-and-axis2-stub-client-tp21172443p21172443.html Sent from the Axis - User mailing list archive at Nabble.com. -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: Interoperability with .NET
Axis 2 is tested and proven interoprability with .net. Have a look at the following news item. I was lucky enough to experience it first hand at the interop plug-fest. http://www.wso2.com/about/news/microsoftinterop/ Except for very few extreme cases WCF and Axis2 demonstrated very good interoperability :). ~Thilina On 5/5/06, GOBE HOBONA [EMAIL PROTECTED] wrote: Anne,you were right there was a problem with the SOAP message. To address theproblem I implemented a new Web Service and a MessageReceiver that builds a SOAP response from scratch. It worked.I think the problem was .NET not managing to deserialise the response fromthe RawXMLINOutMessageReceiver; hence my implementing a new class thatextends AbstractInOutSyncMessageReceiver. So if anybody asks, tell them yes, Axis2 is interoperable with .NETThanks for your help,GobeOn Thu, 4 May 2006 19:24:52 -0400 Anne Thomas Manes wrote:The envelope namespace should be http://schemas.xmlsoap.org/soap/envelope/.If your Axis endpoint is generating a SOAP message with a namespace of http://org.apache.axis2/xsd then you've done something wrong in your code.AnneOn 5/4/06, GOBE HOBONA [EMAIL PROTECTED] wrote: Hello,I am attempting to run the MyService example from a Microsoft.NET client.Iget the following SoapException from .NET when running the echo operation. Envelope namespace http://org.apache.axis2/xsd was unexpected. Expectinghttp://schemas.xmlsoap.org/soap/envelope/ Basically, has anybody successfully read-in SOAP objects from an Axis2 webservice to a .NET client?Any examples of compatibility tests or programs will be much appreciated. -- May the SourcE be with uhttp://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina
RE: Interoperability with .NET
Ensure you ran the WSDL2Java process http://www.codeproject.com/dotnet/NET_WS_with_AXIS.asp?df=100forumid=37 978exp=0select=1284668 -Original Message- From: GOBE HOBONA [mailto:[EMAIL PROTECTED] Sent: Thursday, May 04, 2006 12:57 PM To: axis-user@ws.apache.org Subject: Interoperability with .NET Hello, I am attempting to run the MyService example from a Microsoft.NET client. I get the following SoapException from .NET when running the echo operation. Envelope namespace http://org.apache.axis2/xsd was unexpected. Expecting http://schemas.xmlsoap.org/soap/envelope/; Basically, has anybody successfully read-in SOAP objects from an Axis2 web service to a .NET client? Any examples of compatibility tests or programs will be much appreciated. [This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy.]
Interoperability with .NET
Hello, I am attempting to run the MyService example from a Microsoft.NET client. I get the following SoapException from .NET when running the echo operation. Envelope namespace http://org.apache.axis2/xsd was unexpected. Expecting http://schemas.xmlsoap.org/soap/envelope/; Basically, has anybody successfully read-in SOAP objects from an Axis2 web service to a .NET client? Any examples of compatibility tests or programs will be much appreciated.
Re: Interoperability with .NET
The envelope namespace should be http://schemas.xmlsoap.org/soap/envelope/. If your Axis endpoint is generating a SOAP message with a namespace of http://org.apache.axis2/xsd then you've done something wrong in your code.AnneOn 5/4/06, GOBE HOBONA [EMAIL PROTECTED] wrote:Hello,I am attempting to run the MyService example from a Microsoft.NET client. Iget the following SoapException from .NET when running the echo operation.Envelope namespace http://org.apache.axis2/xsd was unexpected. Expecting http://schemas.xmlsoap.org/soap/envelope/Basically, has anybody successfully read-in SOAP objects from an Axis2 webservice to a .NET client? Any examples of compatibility tests or programs will be much appreciated.
[AXIS 1.x and .NET] Axis Interoperability with .NET Clients using MTOM.
Hi Axis Gurus J I would like to get the company Im currently working at to adopt Axis (instead of say JWSDP) but I need to answer a few questions first. Do we need to use the latest AXIS 1 source to support MTOM or could we use the standard AXIS 1.3? I believe there is some MTOM support in axis 1.3? When using MTOM with AXIS 1.4 on the server and a .NET based client we need all responses to be multi-part encoded, otherwise .NET throws an error in handling the response. AXIS only uses multi-part format when a byte [] return param is present. This is logical but we are wondering if there is a way to force AXIS to use mutli-part encoding without otherwise impacting non-byte [] parameters. We have tried defining this in the WSDL binding but we found that our string return parameter effectively gets converted to an AXIS DataHandler. This avoids the exception in .NET but the client code can no longer understand the returned parameter. I have attached the master WSDL file we are using. The operation in question is called docSourceImport. You will see we worked around the problem by including a dummy byte [] return param called reserved in the docSourceImportResponse. This works but we would prefer a solution that does not impact the API. If anyone could help (or point us in the right direction) with the above, then that would be much appreciated. Many Thanks, Michael Melhem VRDWSAPI.wsdl Description: VRDWSAPI.wsdl
RE: Axis2 interoperability with .Net
Anne,
Im 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:
service
name=AdmitToDpl
description
This is a sample Web Service with two operations,echo and ping.
/description
parameter
name=ServiceClass locked=falseAdmitToDplWebService/parameter
operation
name=admitToDpl
messageReceiver
class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/
/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 dont 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:typesxs: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:typeswsdl:message
name=processDictaphoneResponseMessagewsdl:part
name=part1 element=ns1:processDictaphoneResponse
//wsdl:messagewsdl:message name=processDictaphoneRequestMessagewsdl:part
name=part1 element=ns1:processDictaphoneRequest
//wsdl:messagewsdl:portType
name=DictaphonePortwsdl:operation
name=processDictaphonewsdl:input
message=tns:processDictaphoneRequestMessage /wsdl:output
message=tns:processDictaphoneResponseMessage
//wsdl:operation/wsdl:portTypewsdl:binding
name=DictaphoneBinding
type=tns:DictaphonePortsoap:binding transport=http://schemas.xmlsoap.org/soap/http
style=document /wsdl:operation
name=processDictaphonesoap:operation
name=operation soapAction=processDictaphone
style=document /wsdl:inputsoap:body
use=literal namespace=http://www.org.apache.axis2
//wsdl:inputwsdl:outputsoap:body
use=literal namespace=http://www.org.apache.axis2
//wsdl:output/wsdl:operation/wsdl:bindingwsdl:service
name=Dictaphonewsdl:port name=DictaphonePortType
binding=tns:DictaphoneBindingsoap:address location=http://fh2k039
Re: Axis2 interoperability with .Net
Has anyone else experienced this problem? (Anyone: Please check any WSDL that Axis2 may have generated and look to see if the attributes in the generated schemas are namespace qualified. If so, then this is definitely a bug. But I'm surprised that no one else has mentioned it.)
In the meantime, Paul. I suggest that you handcraft your WSDL.AnneOn 2/14/06, Lessard, Paul
[EMAIL PROTECTED] wrote:
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:
service
name=AdmitToDpl
description
This is a sample Web Service with two operations,echo and ping.
/description
parameter
name=ServiceClass locked=falseAdmitToDplWebService/parameter
operation
name=admitToDpl
messageReceiver
class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/
/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:typesxs: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:typeswsdl:message
name=processDictaphoneResponseMessagewsdl:part
name=part1 element=ns1:processDictaphoneResponse
//wsdl:messagewsdl:message name=processDictaphoneRequestMessagewsdl:part
name=part1 element=ns1:processDictaphoneRequest
//wsdl:messagewsdl:portType
name=DictaphonePortwsdl:operation
name=processDictaphonewsdl:input
message=tns:processDictaphoneRequestMessage /wsdl:output
message=tns:processDictaphoneResponseMessage
//wsdl:operation/wsdl:portTypewsdl:binding
name=DictaphoneBinding
type=tns:DictaphonePortsoap:binding transport=http://schemas.xmlsoap.org/soap/http
style=document /wsdl:oper
Axis2 interoperability with .Net
Hi all, Im trying to use the wsdl.exe prog provided by the .Net SDK and Im getting some errors. Looking through past posts, this doesnt seem to be the tn1 name problem that others had. The error Im 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. Im just starting out in Web Services, so Im not very familiar with WSDL files. Having said that, here is the auto-generated WSDL from Axis2 (sorry it isnt 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:typesxs: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:typeswsdl:message name=processDictaphoneResponseMessagewsdl:part name=part1 element=ns1:processDictaphoneResponse //wsdl:messagewsdl:message name=processDictaphoneRequestMessagewsdl:part name=part1 element=ns1:processDictaphoneRequest //wsdl:messagewsdl:portType name=DictaphonePortwsdl:operation name=processDictaphonewsdl:input message=tns:processDictaphoneRequestMessage /wsdl:output message=tns:processDictaphoneResponseMessage //wsdl:operation/wsdl:portTypewsdl:binding name=DictaphoneBinding type=tns:DictaphonePortsoap:binding transport=http://schemas.xmlsoap.org/soap/http style=document /wsdl:operation name=processDictaphonesoap:operation name=operation soapAction=processDictaphone style=document /wsdl:inputsoap:body use=literal namespace=http://www.org.apache.axis2 //wsdl:inputwsdl:outputsoap:body use=literal namespace=http://www.org.apache.axis2 //wsdl:output/wsdl:operation/wsdl:bindingwsdl:service name=Dictaphonewsdl:port name=DictaphonePortType binding=tns:DictaphoneBindingsoap:address location=http://fh2k039.fhmis.net:8080/axis2/services/Dictaphone //wsdl:port/wsdl:service/wsdl:definitions Anybody have any ideas? Its probably something blindingly obvious, but as said, Im quite new to Web Services. Thank you, Paul Lessard
Re: Axis2 interoperability with .Net
I do have some axis2 web services and web services clients between java and net, so it is possible. You using doc / lit - good. Try the 'free as in beer' soa editor from cape clear - it found 5 errors ;-) . HTH, Robert http://www.braziloutsource.com/ Em Segunda 13 Fevereiro 2006 16:35, o Lessard, Paul escreveu: 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:typesxs: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:typeswsdl:message name=processDictaphoneResponseMessagewsdl:part name=part1 element=ns1:processDictaphoneResponse //wsdl:messagewsdl:message name=processDictaphoneRequestMessagewsdl:part name=part1 element=ns1:processDictaphoneRequest //wsdl:messagewsdl:portType name=DictaphonePortwsdl:operation name=processDictaphonewsdl:input message=tns:processDictaphoneRequestMessage /wsdl:output message=tns:processDictaphoneResponseMessage //wsdl:operation/wsdl:portTypewsdl:binding name=DictaphoneBinding type=tns:DictaphonePortsoap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document /wsdl:operation name=processDictaphonesoap:operation name=operation soapAction=processDictaphone style=document /wsdl:inputsoap:body use=literal namespace=http://www.org.apache.axis2; //wsdl:inputwsdl:outputsoap:body use=literal namespace=http://www.org.apache.axis2; //wsdl:output/wsdl:operation/wsdl:bindingwsdl:service name=Dictaphonewsdl:port name=DictaphonePortType binding=tns:DictaphoneBindingsoap: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
Robert, Thank you for your help. What is doc / lit if you don't mind me asking? Also, are you using the auto-generated wsdl files from the axis2 primary API's or are you creating a WSDL and generating Java code from that? My WSDL file is auto-generated by Axis2, so I don't know how much control I have over editing the WSDL file. Thank you, Paul Lessard -Original Message- From: robert [mailto:[EMAIL PROTECTED] Sent: Monday, February 13, 2006 12:50 PM To: axis-user@ws.apache.org Subject: Re: Axis2 interoperability with .Net I do have some axis2 web services and web services clients between java and net, so it is possible. You using doc / lit - good. Try the 'free as in beer' soa editor from cape clear - it found 5 errors ;-) . HTH, Robert http://www.braziloutsource.com/ Em Segunda 13 Fevereiro 2006 16:35, o Lessard, Paul escreveu: 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:typesxs: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:typeswsdl:message name=processDictaphoneResponseMessagewsdl:part name=part1 element=ns1:processDictaphoneResponse //wsdl:messagewsdl:message name=processDictaphoneRequestMessagewsdl:part name=part1 element=ns1:processDictaphoneRequest //wsdl:messagewsdl:portType name=DictaphonePortwsdl:operation name=processDictaphonewsdl:input message=tns:processDictaphoneRequestMessage /wsdl:output message=tns:processDictaphoneResponseMessage //wsdl:operation/wsdl:portTypewsdl:binding name=DictaphoneBinding type=tns:DictaphonePortsoap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document /wsdl:operation name=processDictaphonesoap:operation name=operation soapAction=processDictaphone style=document /wsdl:inputsoap:body use=literal namespace=http://www.org.apache.axis2; //wsdl:inputwsdl:outputsoap:body use=literal namespace=http://www.org.apache.axis2; //wsdl:output/wsdl:operation/wsdl:bindingwsdl:service name=Dictaphonewsdl:port name=DictaphonePortType binding=tns:DictaphoneBindingsoap: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
All, Sorry... just noticed I pasted the wrong wsdl.exe dump for the WSDL I sent below. The proper wsdl.exe dump is: Microsoft (R) Web Services Description Language Utility [Microsoft (R) .NET Framework, Version 1.1.4322.573] Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. 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 'DictaphoneBinding' from namespace 'http://org.apache.axis2/'. - Unable to import operation 'processDictaphone'. - The element 'http://org.apache.axis2/xsd:processDictaphoneRequest' is missing. Thanks for your help, Paul Lessard P.S. SOA Editor is no longer available from Cape Clear. They replaced SOA with Cape Clear Studio which I believe costs money. There maybe links to archived versions of SOA somewhere but I haven't found any yet. -Original Message- From: robert [mailto:[EMAIL PROTECTED] Sent: Monday, February 13, 2006 12:50 PM To: axis-user@ws.apache.org Subject: Re: Axis2 interoperability with .Net I do have some axis2 web services and web services clients between java and net, so it is possible. You using doc / lit - good. Try the 'free as in beer' soa editor from cape clear - it found 5 errors ;-) . HTH, Robert http://www.braziloutsource.com/ Em Segunda 13 Fevereiro 2006 16:35, o Lessard, Paul escreveu: 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:typesxs: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:typeswsdl:message name=processDictaphoneResponseMessagewsdl:part name=part1 element=ns1:processDictaphoneResponse //wsdl:messagewsdl:message name=processDictaphoneRequestMessagewsdl:part name=part1 element=ns1:processDictaphoneRequest //wsdl:messagewsdl:portType name=DictaphonePortwsdl:operation name=processDictaphonewsdl:input message=tns:processDictaphoneRequestMessage /wsdl:output message=tns:processDictaphoneResponseMessage //wsdl:operation/wsdl:portTypewsdl:binding name=DictaphoneBinding type=tns:DictaphonePortsoap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document /wsdl:operation name=processDictaphonesoap:operation name=operation soapAction=processDictaphone style=document /wsdl:inputsoap:body use=literal namespace=http://www.org.apache.axis2; //wsdl:inputwsdl:outputsoap:body use=literal namespace=http://www.org.apache.axis2; //wsdl:output/wsdl:operation/wsdl:bindingwsdl:service name=Dictaphonewsdl:port name=DictaphonePortType binding=tns:DictaphoneBindingsoap:address location=http://fh2k039.fhmis.net:8080/axis2/services/Dictaphone; //wsdl:port/wsdl:service/wsdl:definitions Anybody have any ideas
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?AnneOn 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:typesxs: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:typeswsdl:message name=processDictaphoneResponseMessagewsdl:part name=part1 element=ns1:processDictaphoneResponse //wsdl:messagewsdl:message name=processDictaphoneRequestMessagewsdl:part name=part1 element=ns1:processDictaphoneRequest //wsdl:messagewsdl:portType name=DictaphonePortwsdl:operation name=processDictaphonewsdl:input message=tns:processDictaphoneRequestMessage /wsdl:output message=tns:processDictaphoneResponseMessage //wsdl:operation/wsdl:portTypewsdl:binding name=DictaphoneBinding type=tns:DictaphonePortsoap:binding transport=http://schemas.xmlsoap.org/soap/http style=document /wsdl:operation name=processDictaphonesoap:operation name=operation soapAction=processDictaphone style=document /wsdl:inputsoap:body use=literal namespace=http://www.org.apache.axis2 //wsdl:inputwsdl:outputsoap:body use=literal namespace=http://www.org.apache.axis2 //wsdl:output/wsdl:operation/wsdl:bindingwsdl:service name=Dictaphonewsdl:port name=DictaphonePortType binding=tns:DictaphoneBindingsoap: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
Hi Paul, see below: Em Segunda 13 Fevereiro 2006 17:33, o Lessard, Paul escreveu: Robert, Thank you for your help. What is doc / lit if you don't mind me asking? Also, are you using the auto-generated wsdl files from the axis2 primary API's or are you creating a WSDL and generating Java code from that? See this article to learn about what doc / lit is and the alternatives: http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/ Doc / lit wrapped is generally the prefered way to go. What works for me is starting out by creating the wsdl file with an editor, and calling wsdl2java and generating the sources. My WSDL file is auto-generated by Axis2, so I don't know how much control I have over editing the WSDL file. Auto generated, from where? Did you click the link in the 'listServices' page? Are you aware that using wsdl is not mandatory? BTW, googling for wsdl editors shows there's plenty out there. HTH, Robert http://www.braziloutsource.com/ Thank you, Paul Lessard -Original Message- From: robert [mailto:[EMAIL PROTECTED] Sent: Monday, February 13, 2006 12:50 PM To: axis-user@ws.apache.org Subject: Re: Axis2 interoperability with .Net I do have some axis2 web services and web services clients between java and net, so it is possible. You using doc / lit - good. Try the 'free as in beer' soa editor from cape clear - it found 5 errors ;-) . HTH, Robert http://www.braziloutsource.com/ Em Segunda 13 Fevereiro 2006 16:35, o Lessard, Paul escreveu: 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:typesxs: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:typeswsdl:message name=processDictaphoneResponseMessagewsdl:part name=part1 element=ns1:processDictaphoneResponse //wsdl:messagewsdl:message name=processDictaphoneRequestMessagewsdl:part name=part1 element=ns1:processDictaphoneRequest //wsdl:messagewsdl:portType name=DictaphonePortwsdl:operation name=processDictaphonewsdl:input message=tns:processDictaphoneRequestMessage /wsdl:output message=tns:processDictaphoneResponseMessage //wsdl:operation/wsdl:portTypewsdl:binding name=DictaphoneBinding type=tns:DictaphonePortsoap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document /wsdl:operation name=processDictaphonesoap:operation name=operation soapAction=processDictaphone style=document /wsdl:inputsoap:body use=literal namespace=http://www.org.apache.axis2; //wsdl:inputwsdl:outputsoap:body use=literal namespace=http://www.org.apache.axis2; //wsdl:output/wsdl:operation/wsdl:bindingwsdl:service name=Dictaphonewsdl:port name=DictaphonePortType binding=tns:DictaphoneBindingsoap: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
