Thank you very much Brian, your tips were very helpful!
-Original Message-
From: Brian Ewins [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 17, 2003 6:15 PM
To: [EMAIL PROTECTED]
Subject: Re: Some help with the usage and notion of FAULT messages!
Apostolopoulos Paris wrote
to notify the client, that something was
not succesful? What I do throw an Axis Fault from my core service
code?
Is it me or I have a feeling that AXIS is a bit restrictive on FAULT
definition and the way it is despatched in the client?
-Original Message-
From: [EMAIL PROTECTED] [mai
Apostolopoulos Paris wrote:
Thank you very much brian!
To tell you the truth I was thinking of changing the Style of my web
service and move to a message driven one where there you have more
processing power to the logic of the request.What do you think!
The answer is just 'it depends'. RPC an
--
From: Brian Ewins [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 17, 2003 4:11 PM
To: [EMAIL PROTECTED]
Subject: Re: Some help with the usage and notion of FAULT messages!
If its a client error, you throw a fault with a fault code beginning
with the string "Client" - eg &qu
help with the usage and notion of FAULT messages!
If its a client error, you throw a fault with a fault code beginning
with the string "Client" - eg "Client.AuthenticationFailure" or
"Client.SomeMadeUpMessage". If you want to send something more than a
simple code,
an Axis Fault from my core service code?
Is it me or I have a feeling that AXIS is a bit restrictive on FAULT
definition and the way it is despatched in the client?
-Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 17, 2003 10:08 AM
To: [EMAIL PROTEC
PROTECTED]]
Sent: Monday, February 17, 2003 10:08 AM
To: [EMAIL PROTECTED]
Subject: Re: Some help with the usage and notion of FAULT messages!
Hi Paris!
Good to know there's another Greek on the list! I think that if your
service will be used by you and only you (that's usually wh
Hi Paris!
Good to know there's another Greek on the list! I think that if your
service will be used by you and only you (that's usually what happens
with final year projects :) ), meaning that you'll be developing both
the provider and the requestor sides, all you have to do is code in
some log
