.
--
View this message in context:
http://www.nabble.com/-Axis2--handlers-per-operation-tp18534755p18651345.html
Sent from the Axis - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
On Fri, Jul 18, 2008 at 11:25 PM, Jack Sprat [EMAIL PROTECTED] wrote:
Hello.
Is there a way to add handlers only for specific operations in a service
and not for all?
For example, I'd like to validate the user/password in the SOAP header on
all operations except the simple echo operation.
I've been down that road and it is not what I am looking for. If I do
this then I need to hard-code the comparison to the SOAP action and I'd
rather not do that. If the operation name ever changes then I'd need to go back
and change the code.
That is not ideal.
Robert Wierschke wrote:
Hi,
Jack Sprat wrote:
Hello.
Is there a way to add handlers only for specific operations in a
service and not for all?
For example, I'd like to validate the user/password in the SOAP header
on all operations except the simple echo operation. I have a handler
set in the axis2.xml confg. file but
Hi,
you may read the SOAP action from the message and decide whether the handler
should do anything or not.
regards
robert
2008/7/18 Jack Sprat [EMAIL PROTECTED]:
Hello.
Is there a way to add handlers only for specific operations in a service
and not for all?
For example, I'd like to
Hello.
Is there a way to add handlers only for specific operations in a service and
not for all?
For example, I'd like to validate the user/password in the SOAP header on all
operations except the simple echo operation. I have a handler set in the
axis2.xml confg. file but that applies to all
