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 interoper
Anne,
you were right there was a problem with the SOAP message. To address the
problem 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 from
the RawXMLINOutMessageRec
.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.
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 attempti
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
Hi Axis Gurus J
I would like to get the company I’m 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 the
rd
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 bee
@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.,
should be:
Can you tell us what you did to generate the WSDL?
Anne
D]
> 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 - goo
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.,
should be:
Can you tell us what you did to generate the WSDL?AnneOn 2/13/06,
Lessard, Paul <[EMAIL PROTECTED]> wrote:
Hi al
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
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
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 L
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 '
14 matches
Mail list logo
