This is the code snippet:
OperationContext opCtx = msgContext.getOperationContext();
MessageContext inMsgCtx;
if(opCtx != null && (inMsgCtx =
opCtx.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE)) !=
null) {
//get the property from the inMsgCtx
}
Thanks,
Ruchith
On 6/30/06, D P <[EMAIL PROTECTED]> wrote:
Would u mind reposting that link? I clicked on it and got a file not found
error. Sorry for the inconvenience.
On 6/29/06, Ruchith Fernando < [EMAIL PROTECTED]> wrote:
>
Hi,
Please see my comments inline:
On 6/28/06, D P <[EMAIL PROTECTED]> wrote:
> 1. Am I correct in assuming the reason why Service context is null is
that
> it is initialized in later in flow phases?
Yes!
The service context is not available at the security phase. This is
because security phase is placed before the dispatch phase and the
context creation occurs right at the end of dispatch phase.
> 2. Can anyone suggest a solution on how to pass the unique id to an
outflow
> handler?
How about the following set of steps:
- Place the created id in the inflow message context at the inflow handler.
- At the outflow handler get hold of the inflow message context and
extract the id value and add it to the message. See here [1] for a
code snippet to extract the in flow msg ctx.
- Also you can maintain a list of valid id's for a certain service as
a list in the configuration context. You have to use configuration
context to store this list since, this is the only context
accessible when you want to authenticate a user with an id in the
inflow handler.
Thanks,
Ruchith
--
www.ruchith.org
[1] http://rafb.net/paste/results/tPlQC035.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
www.ruchith.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
