If this is in Axis2 I'd suggest a handler inserted after the dispatch phase in which case you can get the operation name from the AxisOperation which in turn you can obtain from the MessageContext. In general the SOAPAction can't and shouldn't be relied upon.
David On 05/12/06, D. Kreft <[EMAIL PROTECTED]> wrote:
I'm setting up a table in my database to log accesses to my service. I'm grabbing the username, client host and script name from the SOAP header, but I'd also like to log the name of the method called. What's the best way to do this? Can the SOAPAction HTTP header be reliably counted on for this task, or must I pick apart the SOAP body? Or better yet, is there a pre-fabricated solution I could drop into my service to take care of this for me? Surely this has been done before. :-) -dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
