RE: compatibility with weblogic 6.1 beta

soap.server.ServiceManagerClient http://slivings:7001/soap/servlet/rpcrouter deploy dd.xml Ouch, the call failed: Fault Code = SOAP-ENV:Client Fault String = Unable to resolve namespace URI for 'ns2'. 2) My wl-6.1b will start with xerces in classpath, but same error occurs.

compatibility with weblogic 6.1 beta

Has anyone gotten Apache soap version 2.2 to work with Weblogic 6.1 beta? There seems to be a xerces incompatibility. The weblogic.jar file contains the xerces library. If you put xerces.jar first in the classpath, weblogic won't even start. However, if you put weblogic.jar first in the

usage of custom classes in requests

I would like feedback on the whether or not any of you are using custom classes in your soap calls. While it is definitely convenient on the Apache server side (with its serializers deserializers), it places an extra burden on the client, because now they must have these custom classes on their

RE: usage of custom classes in requests, WSDL issue

, the clients must be changed. This is not very cool, and certainly would lead one to simplify all arguments to/from, as I see things. andrew burke -Original Message- From: Ed Keen [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 05, 2001 7:42 AM To: '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED

RE: WSDL generator

sage-From: Anver Sotnikov [mailto:[EMAIL PROTECTED]]Sent: Wednesday, May 30, 2001 9:26 AMTo: [EMAIL PROTECTED]Subject: RE: WSDL generatorRun it with -? argument. But as I understand it's a Java code generator from WSDL. Ed Keen [EMAIL PROTECTED]

parser exception with base64 encoded string

I have a base64-encoded string that I am trying to pass in my soap call. When rpcrouter gets ahold of it and tries to deserialize the string, I get the below exception. The encoding is set to UTF-8. What else am I missing? org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x0)