Axis2 is highly interoperable with .NET. I don't know why the Mule docs say that either.
I don't like to shoulder the blame, but it seems to me that whoever is providing this endpoint needs to take a look at it. I don't understand why it's sending back a 302. Paul On 4/30/07, Markus F. <[EMAIL PROTECTED]> wrote:
Martin according to http://mule.mulesource.org/display/MULE/Calling+.NET+Web+Services+using+XFire XFire is recommended for .Net interoperabiltiy. But there is no clear reason given (Xfire uses doc/lit ... ) As far as I know Axis2 supports doc/lit too not only rpc (I've never used mule) Markus -- View this message in context: http://www.nabble.com/Axis2-xmlbeans-http-transport-error-302-found-tf3644416.html#a10251025 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
