This is just a follow up on what I found
The OperationDesc in the MessageContext will be null when:
1) The deployed interface/impl has over loaded methods.
2) When the client envelope is well formed (ie SAX parser is
happy) but the method the client is trying to invoke
doesn't
Hello,
I have been running Axis 1.1 for a while... With a handler
that calls messageContext.getOperation() to log the client
method request... The service runs in a WAS 5.1 env on AIX...
Out of the blue I start getting null pointers from the
handler... I traces it down this line:
public void
