RE: Probelm concerning String serialization of Excpetions

I have also noticed this and I have reported it as a bug (to Apache via Bugzilla). The workaround I am using is encapsulating all FAULT data (ie message in thrown exception) with ![CDATA[ and ]]. Sample) Error message Number should be 55 is sent with throw new SOAPException(![CDATA[Number

RE: Exception handling

You should only throw SOAPException's from Java class representing a SOAP service. SOAPExceptions are translated into SOAP Fault codes and text. You can also incorporate your 'UnknownUserException' into a SOAPException. /Micael E. -Original Message- From: Vikram Rajan [mailto:[EMAIL

RE: Exception handling

existing components? it would mean (atleast) re-writing all exception classes. there must be a better way ... if there isnt ... well ... then it should be added. - vikram rajan -- From: Micael Ericsson (QIN) Reply To: [EMAIL PROTECTED] Sent: Monday, September 10, 2001 2

RE: Viewing SOAP Message

Lunch idag eller...? -Original Message- From: Micael Ericsson (QIN) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 04, 2001 9:18 AM To: '[EMAIL PROTECTED]' Subject: RE: Viewing SOAP Message Use TcpTunnelGui class that comes with soap.jar. Simple usage: java

RE: Viewing SOAP Message

talks of a start button. can only find a clear button on the GUI. Am I missing something? thanks, Vikram -- From: Micael Ericsson (QIN) Reply To: [EMAIL PROTECTED] Sent: Tuesday, September 04, 2001 12:47 PM To: '[EMAIL PROTECTED]' Subject: RE: Viewing SOAP

Parameter: order or named

A selfmade service 'StringService' has method 'addStrings(firstString, secondString)', which return a concatinated string. When calling this service using SOAP 'Call' java Class order of parameters is significant. Sending 'secondString' parameter first (in XML message you can se parameter

RE: How to share a variable of a service class among different clients' requests?

Design pattern Singelton solves this. Creating one unique instance that can be acces by several 'services'. This instance 'lives' from first acces until webserver/soap stops. Creating this in Java is easy: - make constructor private so that it is not accesible from outside - make a static

RE: cannot create bean of class org.apache.soap.server.ServiceManager

We are running Tomcat 3.2.3 with Soap 2.2, and everything is running without problems. We upgraded 2 weeks ago from Tomcat 3.2.1 and Soap 2.1, which also was running without problems. We are using Solaris 7 as OS. /Micael E. -Original Message- From: Tibeau Jacques [mailto:[EMAIL

RE: RPC-based SOAP service

The instance is created when first requested. How long its duration is depends on deployment settings which can be: request, session (http session) or application (as long as tomcat lives). /Micael E. -Original Message- From: Walid Rjaibi/Zurich/IBM [mailto:[EMAIL PROTECTED]] Sent:

Problem with and as parameter value

Hello If I call a service and supply a parameter with aa as parameter value this is interpret in XML correctly as lt;aagt;, but reaching Apache Soap (ver 2.2 on tomcat 3.2.3) I get the following error message: Exception: java.lang.Exception:SOAPException= SOAP-ENV:Client, Parsing error,

RE: Problem with and as parameter value

; lt; Unfortunately, I don't recall where the source of it is from. Good Luck! -Original Message- From: Micael Ericsson (QIN) [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 10:53 AM To: '[EMAIL PROTECTED]' Subject: RE: Problem with and as parameter

Parameter order (Java and Call question)

When I call a SOAP service method (running on Apache SOAP 2.2 on tomcat 3.2.3) I must supplied parameters in the same order as the method (in the service deployed Java class) has its parameters defined. Ex) Service urn:math method divide(ini firstValue, int secondValue). I am using apache