Re: Error message not very meaningful

Maurizio Lotauro wrote:

> Is it possible to have a more detailed message?

try
except
  on e: ERemotableException do
    e.FaultDetail

??

/Anders

Hello,

testing a web service as client I get this error when the program 
elaborate the answer:

"Invalid property element: ."

As you can see it is not very meaningful. I need to debug the 
application to discover where the problem lies (it was a boolean 
property with an empty value).
Is it possible to have a more detailed message?
Think about a customer that call you saying that kind of message...

Hello,

I suspect what you're seeing is this from the Delphi RTL:

(Common\RTLConsts.pas)
  SInvalidPropertyElement = 'Invalid property element: %s';

I see that SetEnumProp and GetEnumProp  (TypInfo.pas) use this constant when
they cannot convert a value properly [GetEnumValue(...) fails]. Boolean is
indeed an enumeration in Delphi.

Do you happen to have the stack trace for this failure? I'd like to know the
SOAP code that triggered this and I can investigate.

Cheers,

Bruneau
.

Jean-Marie Babet wrote:
> Hello,

Hello,

> I suspect what you're seeing is this from the Delphi RTL:
> 
> (Common\RTLConsts.pas)
>   SInvalidPropertyElement = 'Invalid property element: %s';

IIRC yes (this happen some day ago)

> I see that SetEnumProp and GetEnumProp  (TypInfo.pas) use this constant
when
> they cannot convert a value properly [GetEnumValue(...) fails]. Boolean is
> indeed an enumeration in Delphi.

This is exactly the case.

> Do you happen to have the stack trace for this failure? I'd like to know
the
> SOAP code that triggered this and I can investigate.

Certainly, but I can do that only next time I go to the customer 
(maximum a few days).

BTW, exists a sort of tool that can simulate a web service?
I mean one that simply answer to a soap request with the content of a 
memo or a file. I have some soap response so it will help a lot to test 
my client without going all the time by the customer.

Hello,

There's another RIO, TLinkedRIO, that we use for this purpose. By default
it's built with the client and server code residing in the same process.
IOW, the Delphi runtime will be both the client and server. However, you can
easily build something whereby the Delphi server response is ignored and
replaced with a pre-existing response. TLinkedRIO already uses files for
both the request and response.

There are other solutions to the issue you're dealing with. Having a
WebServer/WebApplication configured return hardcoded XML is another approach
that I've used before.

Let me know if you need more information and I can provide a sample using
TLinkedRIO.

Cheers,

Bruneau.