Pae Choi wrote:
>
> Just because we are playing in the bleeding edge of open-source development
> and heading to new and emerging standards, the dev. team should not drop the
> existing and running product. In addition to that, the migration should not
> be forced to the "alpha-staged" product nei
+1 to David. Apache/SOAP v2.2 is more stable and functional than Apache/
AXIS. To wit, it is more wide spread and placed in use than AXIS.
In software development process or software engineering, most of SDVs, if
not all, support their existing product while they are developing the
descendent
pro
> The next version of Apache SOAP, i.e., Apache Axis contains this
> functionallity "built in". Under a license that you should find most
> accomodating. ;-)
I was just told that won't work though without also going to Axis for the
SOAP implementation since Axis use JAX-RPC and SOAP 2.2 doesn't
David Wall wrote:
>
>> To generate Apache SOAP servers from WSDL defintions, try using the IBM WSTK
>> utility "servicegen", available at http://www.ibm.com/alphaworks,
>
> Is there anything else that doesn't have a license that restricts use in a
> production environment? This seems like it gets
Despite the apparent structural differences in those two responses,
they're actually the same [as far as section 5 encoding is concerned].
One problem however is that the Apache endpoint is using the 1999
schema version, but IIRC, .NET only supports the 2001 schema version,
you'll need to change y
> To generate Apache SOAP servers from WSDL defintions, try using the IBM
WSTK
> utility "servicegen", available at http://www.ibm.com/alphaworks,
Is there anything else that doesn't have a license that restricts use in a
production environment? This seems like it gets you going, but unless IBM
To: [EMAIL PROTECTED]
> Subject: RE: Interop Problem .NET Client / Apache SOAP Server
>
>
> Hi Martin,
>
> To generate Apache SOAP servers from WSDL defintions, try using
> the IBM WSTK
> utility "servicegen", available at http://www.ibm.com/alphaworks,
&g
erver will then be strictly
conformant to the wsdl - no worrying about namespaces, soapaction, etc.
Tony
> -Original Message-
> From: Martin Centner [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 25, 2002 2:47 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Interop Problem
Simon Fell wrote:
> Make sure your .NET proxy class thinks its doing section 5 encoding,
> it sounds like its trying to do doc/literal.
>
> The method in the proxy class should have a
> System.Web.Services.Protocols.SoapRpcMethodAttribute attribute on it.
hm, this works fine with the HelloWorl
Make sure your .NET proxy class thinks its doing section 5 encoding,
it sounds like its trying to do doc/literal.
The method in the proxy class should have a
System.Web.Services.Protocols.SoapRpcMethodAttribute attribute on it.
Cheers
Simon
www.pocketsoap.com
On Fri, 25 Jan 2002 09:25:04 +0100,
Hi All!
I have got a interoperability problem between a MS.NET client and Apache
SOAP server. The problem is that there are no namespace prefixes in the
element(s) of the RPC response from the Apache SOAP server.
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/1999/X
11 matches
Mail list logo
