Honestly, I'm not sure any of the "advanced" things work with the 
provider/dispatch style services right now.   I KNOW ws-addressing and WS-RM 
don't.  The interceptors for the provider based stuff definitely need some 
work to get them to properly slip into the other pathways.   :-(

Dan



On Wednesday 24 September 2008 1:36:59 pm Lee Breisacher wrote:
> I have a simple WebServiceProvider-based service. I'm using CXF 2.1.2. When
> I add a WSS4JOutInterceptor, I get this NullPointerException:
>
> java.lang.NullPointerException
>         at
> org.apache.cxf.staxutils.StaxUtils.writeStartElement(StaxUtils.java:369) at
> org.apache.cxf.staxutils.StaxUtils.copy(StaxUtils.java:326) at
> org.apache.cxf.staxutils.StaxUtils.copy(StaxUtils.java:314) at
> org.apache.cxf.binding.soap.saaj.SAAJOutInterceptor$SAAJOutEndingIntercepto
>r.handleMessage(SAAJOutInterceptor.java:161) at
> org.apache.cxf.binding.soap.saaj.SAAJOutInterceptor$SAAJOutEndingIntercepto
>r.handleMessage(SAAJOutInterceptor.java:127) at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChai
>n.java:220) at
> org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingC
>hainInterceptor.java:74) at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChai
>n.java:220) at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationO
>bserver.java:78) at
> org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestinati
>on.java:92) at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(Servle
>tController.java:283) at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController
>.java:166) at
> org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServl
>et.java:174) at
> org.apache.cxf.transport.servlet.AbstractCXFServlet.doPost(AbstractCXFServl
>et.java:152) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362) at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at
> org.mortbay.jetty.Server.handle(Server.java:324)
>         at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505) at
> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java
>:843) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:647) at
> org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211) at
> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380) at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395
>) at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:
>450) Sep 24, 2008 10:31:55 AM
> org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback onClose
>
> I'm not actually doing anything with WSS yet - just inserted the
> interceptor in preparation for doing some real WSS stuff.
>
> I found CXF-1538 (http://issues.apache.org/jira/browse/CXF-1538), which
> looks sortof like the same problem, but it appears to have been fixed
> already.
>
> Am I doing something wrong or is this a bug?
>
> Thanks,
>
> Lee



-- 
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog

Reply via email to