Handling Faults

I am getting an "Unable to resolve target: null" error, and saw that the troubleshooter said there was an element in the Fault to look at for the stack trace. However, none of the samples seem to show how to do anything but getting the fault error code and message. Any short snippets of accessing

RE: Problem

I don't think so. This bug is in Xerces, I have submitted a bug report on it. -Original Message- From: Scott Nichol [mailto:[EMAIL PROTECTED]] Sent: 03 July 2001 16:55 To: [EMAIL PROTECTED] Subject: Re: Problem This was a problem that has been fixed Apache SOAP 2.2. Scott Nichol -

Error during Envelope.unmarshall()

Hell All, I have a Servlet that accepts a SOAP Message, and using the following function parses the message and constructs a string to return back to the calling function. The function is as follows: //***CODE START** public

cvs commit: xml-soap/java/src/org/apache/soap Constants.java

rubys 01/07/04 08:03:41 Modified:java/src/org/apache/soap Constants.java Log: timeInstant became dateTime in 2001 Revision ChangesPath 1.22 +1 -1 xml-soap/java/src/org/apache/soap/Constants.java Index: Constants.java ===

Artifacts for Server

Simple question I didn't see a clear answer to. I have a set of code artifacts for the server to expose through SOAP-RPC. Say, a class called CDCatalog in the javaxml2 package (so javaxml2.CDCatalog). I've got my deployment descriptor all set up, and registered with the server. My question is whe

Re: Problem

The other response on the mailing list was correct. This is a new error arising from Apache SOAP 2.2 support of JAXP. I do not know whether the error is unique to a particular XML processor's implementation of JAXP, or whether all JAXP processors have this problem. The best I can do is suggest

Re: Exception while calling ServiceManagerClient

Your client is loading an XML parser that does not support namespaces. Be certain your classpath has a supported parser before any other parser, and check that there is no parser in $JAVA_HOME/jre/lib. Scott - Original Message - From: "Ralf Bierig" <[EMAIL PROTECTED]> To: <[EMAIL PROTEC

RE: NoSuchMethodError in QName of SOAP2.2

Hi, there are lot of problems with SOAP 2.2. This error might be of 2 reasons 1. You have not exposed the method in Deployment descriptor. 2. The class has not been put in the web-inf classes . if not, try using the xml apache for soap 1.4 version. This should solve the problem. Raja Innova So

Sorry this is a test

test

Re: SOAP 2.2 & Tomcat Error: <404 Not found>

Thanks, this was right. I have forgotten to tarnsfer the code, so it fits to tomcat restrictions. Thank you! But I have now anthter problem: I will post it separately in another mail. Greetings Ralf --- Scott Nichol <[EMAIL PROTECTED]> wrote: > The URI your application request apparently begin