)
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
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
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
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
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
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
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
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
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
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
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
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
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
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
14 matches
Mail list logo
