Just committed a fix. In this case, the conduit could definitely be null so check for it.
Dan On Monday 25 October 2010 8:45:07 am Milan Duriancik wrote: > Hello, > > I'm testing WS-Addressing with JMS Transport, > all works fine for request/response operations, > but when I call a OneWay operation, I get a NPE. > > (When I disable ws-addressing feature it works fine.) > > > The Exception: > > java.lang.NullPointerException > at > org.apache.cxf.interceptor.OneWayProcessorInterceptor.handleMessage(OneWayP > rocessorInterceptor.java:89) at > org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChai > n.java:247) at > org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationO > bserver.java:113) at > org.apache.cxf.transport.jms.JMSDestination.onMessage(JMSDestination.java:2 > 20) at > org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeL > istener(AbstractMessageListenerContainer.java:535) at > org.springframework.jms.listener.AbstractMessageListenerContainer.invokeLis > tener(AbstractMessageListenerContainer.java:495) at > org.springframework.jms.listener.AbstractMessageListenerContainer.doExecute > Listener(AbstractMessageListenerContainer.java:467) at > org.springframework.jms.listener.AbstractPollingMessageListenerContainer.do > ReceiveAndExecute(AbstractPollingMessageListenerContainer.java:323) at > org.springframework.jms.listener.AbstractPollingMessageListenerContainer.re > ceiveAndExecute(AbstractPollingMessageListenerContainer.java:261) at > org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessa > geListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1056) > at > org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessa > geListenerInvoker.run(DefaultMessageListenerContainer.java:952) at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.j > ava:886) at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java: > 908) at java.lang.Thread.run(Thread.java:619) > > > > Looking closer at the ws-addressing headers I found: > > ReplyTo:Address -> http://www.w3.org/2005/08/addressing/none > > I think OneWayProcessorInterceptor is trying to obtain a back channel with > this uri, > and as there's no conduit initiator for > http://www.w3.org/2005/08/addressing/none, > conduitInitiator.getConduit => NPE > > > Has somebody a similar problem? > Is this a bug or have I some problem in my configuration? > > (JAX-WS frontend, CXF 2.3.0, Spring 3.0.4, ActiveMQ , JDK 1.6.0_20) > > > Thanks, > > > Milan -- Daniel Kulp [email protected] http://dankulp.com/blog
