wrote:
Remo,
Can you send me your code for the exception handler since I am unable to
make mine work and need some thing which is working and looks like u are
making a similar webservice (Message style).
Thanx.
dumdum420
-Original Message-
From: Bhanu Pabreja [mailto:[EMAIL PROTECTED]
le to
make mine work and need some thing which is working and looks like u are
making a similar webservice (Message style).
Thanx.
dumdum420
-Original Message-
From: Bhanu Pabreja [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 10, 2003 12:30 PM
To: [EMAIL PROTECTED]
Subject: RE: Exception handl
: Thursday, July 10, 2003 12:30 PM
To: [EMAIL PROTECTED]
Subject: RE: Exception handling strategy question
the invoke() throws AxisFault ; this is what the api also shows. I am using
AXIS 1.1 and I also do not have a clue which SOAP level I am using.
Kindly clarify this. I have only one method
waiting for some one to reply on this topic ...
dumdum420
-Original Message-
From: Bhanu Pabreja [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2003 3:03 PM
To: Axis-User
Subject: FW: Exception handling strategy question
The AxisFault actually extends RemoteException so it is fine
ptions and
can design my webservice in a straight manner.
Thanx in advance.
dumdum420
-Original Message-
From: Bhanu Pabreja [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2003 12:30 PM
To: [EMAIL PROTECTED]
Subject: RE: Exception handling strategy question
the invoke() throws AxisFault
To: [EMAIL PROTECTED]
Subject: Re: Exception handling strategy question
Here's what I did:
Since the ..invoke() call throws a RemoteException
I used
... throws RemoteException {
try {
...
}
catch (RemoteException e1) {
sb1 =
MessageContext.getCurrentContext().getResponseMe
Here's what I did:
Since the ..invoke() call throws a RemoteException
I used
... throws RemoteException {
try {
...
}
catch (RemoteException e1) {
sb1 =
MessageContext.getCurrentContext().getResponseMessage().getSOAPPart().getEnvelope().getBody();
SOAPFault fault = sb1.a
Well I saw this thread in the mail archive ... so got to ask a question.
Like remo i have a similar kind of service (message style) with only once
service operation exposed
Document fetchData(Document doc) throw AxisFault{}
Now Remo you must have implemented your exception handling already whi
SOAP fault
information as a message . A fault message is always formating using
the document style.
Anne
- Original Message -
From:
remko
de knikker
To: [EMAIL PROTECTED]
Sent: Monday, June 30, 2003 4:48 PM
Subject: Re: Exception handling strategy
question
I am
your exceptions, and then tell Axis to
map the exceptions to the faults accordingly.
Anne
-
Original Message -
From:
remko de knikker
To:
[EMAIL PROTECTED]
Sent:
Friday, June 27, 2003 1:31 PM
Su
l Axis to map the exceptions to the faults accordingly.
Anne
- Original Message -
From: remko de knikker
To: [EMAIL PROTECTED]
Sent: Friday, June 27, 2003 1:31 PM
Subject: Re: Exception handling strategy question
Situation:OK, so far this helped, and pointed out the right direction
l Axis to map the exceptions to the faults accordingly.
Anne
- Original Message -
From: remko de knikker
To: [EMAIL PROTECTED]
Sent: Friday, June 27, 2003 1:31 PM
Subject: Re: Exception handling strategy question
Situation:OK, so far this helped, and pointed out the right direction
Original Message -
From:
remko de knikker
To:
[EMAIL PROTECTED]
Sent:
Friday, June 27, 2003 1:31 PM
Subject:
Re: Exception handling strategy question
Situation:OK, so far this helped, and pointed
out the right direction in which to go.
ap
your various exceptions to specific SOAP fault messages.
[1] http://www.w3.org/TR/SOAP/#_Toc478383510
Regards,
Anne
- Original Message -
From: "George Jagodzinski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 24, 2003 3:22 PM
Subject: RE: Except
:
remko
de knikker
To: [EMAIL PROTECTED]
Sent: Friday, June 27, 2003 1:31 PM
Subject: Re: Exception handling strategy
question
Situation:OK, so far this helped, and pointed out
the right direction in which to go. I had seen the SOAP Faults and understand
now when to use them
dzinski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 24, 2003 3:22 PM
Subject: RE: Exception handling strategy question
if you are refering to business logic that happens after the request has
been accepted I would say that the best way is to return some t
ohso thats why they keep writing all of these standards. I guess I
actually have to read them.
Thanks
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2003 3:53 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Exception handling
l Message -
From: "George Jagodzinski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 24, 2003 3:22 PM
Subject: RE: Exception handling strategy question
> if you are refering to business logic that happens after the request has
> been accepted I would
.
--George
-Original Message-
From: remko de knikker [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2003 3:22 PM
To: [EMAIL PROTECTED]
Subject: Exception handling strategy question
when implementing a web service and a ws client, what is the general
design principle for exception
when implementing a web service and a ws client, what is the general
design principle for exception handling, when
1. when user entered a non-valid input value, for instance it doesn't
exist in the database?
Do I simply through a SOAPFault or is it better to append my own
tag?
2. as a client,
20 matches
Mail list logo
