As mentioned in my previous mail,
MessageContext inMessageContext = MessageContext.getCurrentMessageContext();
OperationContext operationContext = inMessageContext.getOperationContext();
MessageContext outMessageContext = operationContext
.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);

~Thilina

On 3/1/07, Punnoose, Roshan <[EMAIL PROTECTED]> wrote:
Sorry to keep bringing this up, but how do I get access to the
OutMessageContext. I'm assuming that the
MessageContext.getCurrentContext() will only bring back the
InMessageContext?

Roshan Punnoose
Phone: 301-497-6039

-----Original Message-----
From: Punnoose, Roshan [mailto:[EMAIL PROTECTED]
Sent: Friday, February 23, 2007 9:47 AM
To: [email protected]; [EMAIL PROTECTED]
Subject: RE: setOperationContext

If this is a static method, how can multiple requests to one service
work? Just wondering, how I could access the MessageId for different
requests to the same service. Thanks!

Roshan Punnoose
Phone: 301-497-6039
-----Original Message-----
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 11:06 PM
To: [email protected]
Subject: Re: setOperationContext

That's outdated!. please use MessageContext.getCurrentContext() from
inside your service method (when Axis2 calls your service method.)

thanks,
dims

On 2/22/07, Kang, Kamaljeet K. <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I would like to access service context on the skeleton side. I
followed
> the documentation ("http://wso2.org/library/259";) and added
> 'setOperationContext(OperationContext opCtxt)' in the skeleton class
but
> the method is never called. Is this the correct way to access Context
on
> the server side?
>
>
> Thanks
>
> Kamal Kang
>
> ============================================================
> The information contained in this message may be privileged
> and confidential and protected from disclosure. If the reader
> of this message is not the intended recipient, or an employee
> or agent responsible for delivering this message to the
> intended recipient, you are hereby notified that any reproduction,
> dissemination or distribution of this communication is strictly
> prohibited. If you have received this communication in error,
> please notify us immediately by replying to the message and
> deleting it from your computer. Thank you. Tellabs
> ============================================================
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services
Developers

---------------------------------------------------------------------
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]




--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to