Re: fault listener

Ok Scott,

Thanks very much. I will try to make minimal examples that reproduces the
errors, and investigate it. The big problem is I don't know much about serialization
and deserialization; I am just a SOAP user.

Do you have any problem that I post some results of the examples, if I can't
find the solution?, or do you prefer waiting until you have some time to
investigate?

Thanks for YOUR patience,

tizo



>-- Mensaje original --
>Reply-To: [email protected]
>From: "Scott Nichol" <[email protected]>
>To: <[email protected]>
>Subject: Re: fault listener
>Date: Fri, 11 Jun 2004 09:45:36 -0400
>
>
>
>For #2, I cannot fault your logic, but it since you are getting a Node
instead
>of a Parameter, I think you will need to handle both the case when you
get
>a Parameter and when you get a Node.  As I said before, the de-serialization
>looks like it will produce a Node whenever it cannot produce a Parameter,
>and this may be one of those cases.
>
>I hope to investigate this in more depth soon, but right now I am afraid
>I just do not have the time.
>
>Thanks for your patience.
>
>Scott Nichol
>
>Do not send e-mail directly to this e-mail address,
>because it is filtered to accept only mail from
>specific mail lists.
>----- Original Message ----- 
>From: <[email protected]>
>To: <[email protected]>
>Sent: Tuesday, June 08, 2004 4:34 PM
>Subject: Re: fault listener
>
>
>Scott,
>
>I think that I was not clear enough (sorry about my english).
>
>I have two problems, which I'll try to explain again. 
>
>The scenario is the following: I am trying to catch a server exception
in
>the client side; not the SOAP Fault, but the original server exception.
>So, in any of the cases that I am testing, I am forcing the server to throw
>an exception. To catch the exception from client, I am trying using ExceptionFaultListener.
>I thought that in that way, I could obtain the Fault in the client side,
>obtain the detail entries from it (with getDetailEntries method), take
the
>first element, which would be a Parameter, and take the orignal exception
>from that Parameter. Is that reasoning right? Supposing that it is right,
>the problems that I am having are:
>
>1-Using the production version of Apache SOAP, I couldn't obtain the Fault
>in the client, because an exception is throwed at the moment of the invocation
>(i.e: when the method invoke is called). I have posted the message of this
>exception earlier, but if you want, I could post it again.
>
>2-Using the nightly build of Apache SOAP, I could obtain the Fault (what
>it is supposed to do), and the message of the Fault is right (it tells
the
>original exception). In the detail entries Vector of the Fault, there is
>only one element (of class org.apache.crimson.tree.ElementNode2), and it
>contains the stackTrace of the exception. The stackTrace is right, it says
>what it should said; but the problem is that, if my reasoning is right,
>the element of the detail entries Vector should not be a stackTrace; it
>should be a Parameter from which I could take the orignial exception, shouldn't
>it?
>
>I hope that this make things clearer.
>
>Thanks very much,
>
>tizo
>
>
>
>>-- Mensaje original --
>>Reply-To: [email protected]
>>From: "Scott Nichol" <[email protected]>
>>To: <[email protected]>
>>Subject: Re: fault listener
>>Date: Mon, 7 Jun 2004 23:59:18 -0400
>>
>>
>>----- Original Message ----- 
>>From: <[email protected]>
>>To: <[email protected]>
>>Sent: Monday, June 07, 2004 7:55 PM
>>Subject: Re: fault listener
>>
>>
>>Scott,
>>
>>>>>>
>>I have tried with the nightly build of Apache SOAP, and there is not more
>>exception in the client when I use ExceptionFaultListener, and there is
>>a exception in the server
>><<<<
>>
>>What is the stack dump from the server exception?  The nightly build should
>>have more useful information in the dump than the 2.3.1 release had.
>>
>>>>>>
>> (is that a bug in the production version?, if
>>it is, how could I fix that?)
>><<<<
>>
>>You need to post the stack dump for anyone to determine the nature of
the
>>problem.
>>
>>>>>>
>>, but I still have a problem:
>>
>>I have seen the code of ExceptionFaultListener, and it takes the original
>>exception, wraps it in a Parameter, puts the Parameter in a Vector, and
>>puts the last one in the detail entries of the Fault (with method setDetailEntries).
>>In the client side, when I've got a Fault, I get the detail entries Vector
>>(with method getDetailEntries), take the first element of this Vector
(the
>>only one), and it is not of class Parameter; why?, shouldn't it be a Parameter?
>>Anyway, this object (the first one of the detail entries Vector) is of
>class
>>org.apache.crimson.tree.ElementNode2.
>><<<<
>>
>>It will be a Parameter, unless an exception is thrown trying to de-serialize
>>a detail as a Parameter, in which case it will be kept as an Element.
>>
>>Scott Nichol
>>
>>Do not send e-mail directly to this e-mail address,
>>because it is filtered to accept only mail from
>>specific mail lists.
>>
>
>
>