Hmmm... what you are doing should work. As an easy workaround, you can always call PhaseInterceptorChain.getCurrentMessage() to get the current CXF Message and pull values from there. You would need to use the CXF Message.* keys and not the JAX-WS keys.
If you want to stick with JAX-WS, you can just do: WebServiceContext context = new org.apache.cxf.jaxws.context.WebServiceContextImpl(); and use that. Dan On Tuesday, October 18, 2011 1:23:24 PM Kent Närling wrote: > Hi, thanks for the quick answer, however: > > On 18 October 2011 12:52, Sergey Beryozkin <[email protected]> wrote: > > Hi, > > > > On 18/10/11 08:51, Kent Närling wrote: > >> Also, another question: > >> > >> How do I get the Context without injection? > >> > >> We are currently not running our service in Spring, so we need to get > >> the Context some other way... > > > > I'm presuming you are referring to JAX-WS WebServiceContext, given that > > you mention SOAP... I think JAX-WS will just inject it into a private > > field even without Spring being involved... Possible for JAX-RS too > > I tried both: > > private @Resource > MessageContext context; > > and > > private @Resource > WebServiceContext context; > > in the class implementing the @Webservice interface and both of the fields > are nulll... > > FYI we start our WS as a plain java process and use Endpoint.publich() just > to publish our endpoints... > > > Cheers, Sergey > > > >> On 18 October 2011 09:05, Kent > >> Närling<kent.narling@seamless.**se<[email protected]>>>> > >> wrote: > >> > >> Hi, > >> > >>> What is the status of CXF continuations and where do I find the best > >>> documentation on how to use it? > >>> > >>> Is the support for continuations usable for production? I see some > >>> mentionings of beta status etc but that might be outdated? > >>> > >>> Also, I tried to look for documentation how to use it but the best I > >>> found > >>> was the "musings" on Sergey Beryozkin's blog from 2008, which is > >>> very > >>> brief? > >>> Surely there must be something better with samples etc? > >>> > >>> Lastly, how good of an option IS continuations for writing eg a > >>> truly > >>> asynchronous SOAP proxy (eg that gets SOAP requests and proxies into > >>> another > >>> asynchronous protocol)? > >>> I mean mainly for performance point of view? > >>> > >>> Is there no truly message-based interface for SOAP processing? > >>> > >>> Best regards, > >>> Kent -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
