Hi Ruchith,
I also expected the phases you mentioned. But when I check the
executionChain in the messagecontext while debugging I only see the
phases I mentioned before. For some reason sandesha2 alters the phases
of the messages during invocation.
Before sandesha2 was added the execution chain was as you described.
Thanks,
Lennard.
||
Ruchith Fernando wrote:
Hi Lennard,
On 8/2/06, Lennard IJsselstein <[EMAIL PROTECTED]> wrote:
Hi all,
We are currently using both the Sandesha2 and the Rampart module.
The problem we are facing now is when we send a webservice call the
following happens:
- The CreateSequence soapmessage is send to the Axis2 servlet and is
correctly processed.
As expected the following axis2 phases are hit:
Transport, Security, RMPhase OperationInPhase
- The soapmessage with the actual webservice call is send to the Axis2
servlet.
The following phases are hit:
soapmonitorPhase, RMPhase, OperationInPhase.
- The TerminateSequence soapmessage is send to the Axis2 servlet and is
correctly processed.
As expected the following axis2 phases are hit:
Transport, Security, RMPhase, OperationInPhase
Our question is:
Why does the 'normal' soapmessage not run through the Security
phase?
IMHO the request message should go through the following phases :
Transport, Security, PreDispatch, Dispatch, OperationInPhase
Transport and Dispatch phases are used to dispatch and since you have
not mentioned any of these in the phases that the soap message hit I
wonder how the request reached the OperationInPhase.
Thanks,
Ruchith
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
