Ne'er mind...I got this figured out based upon a response to another question.
The solution is to create a handler that inherits from BasicHandler. :-)
-dan
On 12/5/06, D. Kreft <[EMAIL PROTECTED]> wrote:
On 12/5/06, David Illsley <[EMAIL PROTECTED]> wrote:
> If this is in Axis2 I'd suggest a
On 12/5/06, David Illsley <[EMAIL PROTECTED]> wrote:
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
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
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 t