David, I'm sorry, I was wrong. Actually it is available :).
Thanks, Michele Michele Michele Mazzucco wrote: > David, > > I realized that the first element local name is actually the operation > name, and not the ws action. > > Thanks, > Michele > > David Illsley wrote: >> In short, no. >> >> The only way to get the wsaddressing action is to read the contents of the >> wsa:Action element. >> That probably doesn't help :-( but it's the case. > > Yes, unfortunately it doesn't help :( since it seems to me that the > wsa:Action is not available before the transport/security phase. > > > Regards, > Michele >> David Illsley >> >> Michele Mazzucco <[EMAIL PROTECTED]> wrote on 06/29/2006 10:24:19 >> AM: >> >>> And add "urn:" before it? >>> >>> Michele >>> >>> Michele Mazzucco wrote: >>>> Hi all, >>>> >>>> I've got a handler running before the transport phase. How can I get >> the >>>> WS addressing action there as the <wsa:Action> element is created >>>> later? Is it enough to get the first element local name of the SOAP >> body? >>>> Thanks, >>>> Michele >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
