Strange... It looks like we're still loosing the security info in the
message context. For the moment I have to put a hold on the
implementation of Sandesha2 due to other project priorities. I will look
further into it when time comes. I'll keep you posted.
Thanks for all the replies,
Lennard.
Chamikara Jayalath wrote:
On 8/4/06, *Ruchith Fernando* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
On 8/3/06, L YSSELSTEIN <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
> Hi Ruchith,
>
> I looked at the website and understand how to fetch the username
from the message context.
> I'm afraid the problem doesn't change however.
>
> Because when the message receiver method is reached the security
handler is not processed. Sandesha has called the handler in the
create sequence call, so won't call the security handler when it
resumes application messages of a RM sequence. In other words
there is no user information in the message context.
Hmm... IMHO we should use the original msgCtx when resuming the
aplication message. Chamikara, what do you think?
Yes. It is the original Message Context that is used when resuming.
No information saved there can get lost.
Chamikara
Thanks,
Ruchith
--
www.ruchith.org <http://www.ruchith.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
