Deepal,
I'm sorry, but maybe there's a misunderstanding. Which version should I
use, 1.1RC* or 1-snapshot? In what do they differ?
Why I don't see the getCurrentContext() method in the MessageContext class?
Thanks,
Michele
Deepal Jayasinghe wrote:
Hi Michele;
yes , we removed that
Hi Michele ;
You need to use Nightly build , we didnt have that in 1.1 RC*
Thanks
Deepal
Deepal,
I'm sorry, but maybe there's a misunderstanding. Which version should I
use, 1.1RC* or 1-snapshot? In what do they differ?
Why I don't see the getCurrentContext() method in the MessageContext
Hi all,
after a few weeks I've updated my axis2 libs and I've found out that
the Service interface has been removed while a new one has been added
(ServiceLifeCycle). Unfortunately the new interface does not provide
any facility to obtain the operation/message context (i.e. the old
Hi Michele;
yes , we removed that interface and provide an easy way to access
message context in side the service impl class.
What you have to do is call
MessageContext.getCurrentContext();
It will give you the message context you want to access.
Hi all,
after a few weeks I've updated my axis2
Hi all,
the method declared into the Service interface does not throw any
exception, while the usual implementation:
this.inMsgCtx =
opctx.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE)
does. Is it possible to remove the throws clause from the
OperationContext.getMessageContext()
