You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Mayank Thakore <ma...@huawei.com> on 2008/02/12 09:33:34 UTC
message context is null
Hi,
I inject the context into my service impl like this:
@Resource
private WebServiceContext context;
The context is available during invocation, but when I do:
MessageContext messageContext = context.getMessageContext();
The messageContext comes up null in Solaris. In Windows it comes fine.
What am I doing wrong?
Mayank
****************************************************************************
****************************
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
Re: message context is null
Posted by Daniel Kulp <dk...@apache.org>.
Yep. That would do it. The creation of the JAXWS WebServiceContext is
taken care of in the JAXWSMethodInvoker. I'm not sure what your
custom invoker was doing, but possibly subclassing JAXWSMethodInvoker
might make it work. In anycase, I'd be more than happy to refactor the
JAXWSMethodInvoker a little bit to make subclassing it easier to get it
to work. If you have suggestions (or better yet: a patch) feel free to
post them here or in JIRA.
Dan
On Tuesday 12 February 2008, Mayank Thakore wrote:
> Found the panga. Seems my custom invoker was eating up the context.
> Works like a charm after removing the custom invoker.
>
> Regards
> Mayank
>
> -----Original Message-----
> From: Mayank Thakore [mailto:mayankt@huawei.com]
> Sent: Tuesday, February 12, 2008 14:04
> To: cxf-user@incubator.apache.org
> Subject: message context is null
>
> Hi,
>
> I inject the context into my service impl like this:
>
> @Resource
> private WebServiceContext context;
>
> The context is available during invocation, but when I do:
>
> MessageContext messageContext = context.getMessageContext();
>
> The messageContext comes up null in Solaris. In Windows it comes fine.
>
> What am I doing wrong?
>
> Mayank
>
> **********************************************************************
>****** ****************************
> This e-mail and attachments contain confidential information from
> HUAWEI, which is intended only for the person or entity whose address
> is listed above. Any use of the information contained herein in any
> way (including, but not limited to, total or partial disclosure,
> reproduction, or dissemination) by persons other than the intended
> recipient's) is prohibited. If you receive this e-mail in error,
> please notify the sender by phone or email immediately and delete it!
--
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog
RE: message context is null
Posted by Mayank Thakore <ma...@huawei.com>.
Found the panga. Seems my custom invoker was eating up the context. Works
like a charm after removing the custom invoker.
Regards
Mayank
-----Original Message-----
From: Mayank Thakore [mailto:mayankt@huawei.com]
Sent: Tuesday, February 12, 2008 14:04
To: cxf-user@incubator.apache.org
Subject: message context is null
Hi,
I inject the context into my service impl like this:
@Resource
private WebServiceContext context;
The context is available during invocation, but when I do:
MessageContext messageContext = context.getMessageContext();
The messageContext comes up null in Solaris. In Windows it comes fine.
What am I doing wrong?
Mayank
****************************************************************************
****************************
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!