Interop Problem .NET Client / Apache SOAP Server

2002-01-25 Thread Martin Centner
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 return element(s) of the RPC response from the Apache SOAP server. SOAP-ENV:Envelope

Re: Interop Problem .NET Client / Apache SOAP Server

2002-01-25 Thread Simon Fell
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

About array: anyType

2002-01-25 Thread dovle
Hi all, I have one question to ask: When the apache soap finds a tag that has the xsi:type=SOAP-ENC:Array and the SOAP-ENC:arrayType=xsd:anyType[10] it throws an exception saying that the type is unsuported. Question: how can I make apache soap interpret this kind of that as a Vector and

soap.jar and xmlparserv2-soap.jar

2002-01-25 Thread Dilova, Tereza (BG)
Hi to all ! Is there anyone using Oracle iAS10222, Apache and Jserv ? Can you send me soap.jar xmlparserv2-soap.jar ?

Re: Interop Problem .NET Client / Apache SOAP Server

2002-01-25 Thread Martin Centner
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 HelloWorld

RE: encoding styles for SOAP messages ..

2002-01-25 Thread Anne Thomas Manes
The spec only identifies Literal and SOAP Section 5 encoding, but it also says that SOAP messages can use other encodings. Your toolkit must support Literal and SOAP Section 5, and you should provide a mechanism to allow developers to specify and use alternate encodings. Anne -Original

RE: Interop Problem .NET Client / Apache SOAP Server

2002-01-25 Thread Tony Hong
Hi Martin, To generate Apache SOAP servers from WSDL defintions, try using the IBM WSTK utility servicegen, available at http://www.ibm.com/alphaworks, which will create everything you need , including the deployment descriptor. You then simply supply the implementation, and the server will then

RE: Interop Problem .NET Client / Apache SOAP Server

2002-01-25 Thread Tony Hong
Sorry, one clarification - Pull down the package 'Web Services Toolkit' from alphaWorks. servicegen is a utility bundled in the package. Tony -Original Message- From: Tony Hong [mailto:[EMAIL PROTECTED]] Sent: Friday, January 25, 2002 5:12 AM To: [EMAIL PROTECTED] Subject: RE:

Re: Interop Problem .NET Client / Apache SOAP Server

2002-01-25 Thread David Wall
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

Re: Interop Problem .NET Client / Apache SOAP Server

2002-01-25 Thread Simon Fell
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

Re: Interop Problem .NET Client / Apache SOAP Server

2002-01-25 Thread Sam Ruby
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 you

Re: Interop Problem .NET Client / Apache SOAP Server

2002-01-25 Thread David Wall
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,

Re: Interop Problem .NET Client / Apache SOAP Server

2002-01-25 Thread Pae Choi
+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

Re: Interop Problem .NET Client / Apache SOAP Server

2002-01-25 Thread Sam Ruby
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 neither.

IBM wsdl2java and Microsoft .Net .wsdl files

2002-01-25 Thread Gary Feldman
Has anyone been able to get the IBM wsdl2java tool working on the Microsoft .Net Services wsdl files (the files they use and ship in the .Net Services SDK to describe their own services, not the demo/example files)? For that matter, has anyone found a WSDL to Java processor that works on these

Apache Soap 2.2 questions

2002-01-25 Thread Jeff Corliss
Hi all, New to the project and the list. Have everything running ok and even wrote small service/client. Some questions I have though: - Is this project dead? I know the list is active but with a last release from May 2001, it seems like it might be. If it is dead, what is being used

JNI under Apache SOAP 2.2 Tomcat

2002-01-25 Thread Thomas Thornbury
Hi all, I have a SOAP app that runs fine under the configuration above under Win2K. However I'm porting it to HPUX. It has a executable DLL called via JNI under Win2K. I've recompiled the library under HPUX and created a .so file. Unfortunately SOAP can't find it. I tried setting

Re: Apache Soap 2.2 questions

2002-01-25 Thread Fred Meredith
I don't think this project is dead. There is another Apache project, Axis that will eventually replace this one (I assume). Axis just recently released an alpha3 which is functionally complete. - Is this project dead? I know the list is active but with a last release from May 2001, it