[
https://issues.apache.org/jira/browse/CXF-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210300#comment-13210300
]
Aki Yoshida commented on CXF-4023:
----------------------------------
Hi Michael,
thanks for the update. That's a good news.
I just submitted a fix for this NPE issue in trunk and 2.5.3-SNAPSHOT so that
the RMException with the message regarding the wrong namespace usage will be
reported in this case.
regards, aki
> invalid ProtocolVariant causes NullPointerException in RMSoapInterceptor
> ------------------------------------------------------------------------
>
> Key: CXF-4023
> URL: https://issues.apache.org/jira/browse/CXF-4023
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.5.1
> Environment: Windows XP
> java version "1.6.0_26"
> Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Java HotSpot(TM) Client VM (build 20.1-b02, mixed mode, sharing)
> Reporter: Michael Heß
> Assignee: Aki Yoshida
>
> If a WS-RM request contains a mixture of Protocol Variants (for WS-A and
> WS-RM) that is unknown to org.apache.cxf.ws.rm.ProtocolVariation, the
> following NPE is raised.
> Interceptor for
> {http://ws.ra.bsg.oslee.orga.com/}ReloadAccountService#{http://ws.ra.bsg.oslee.orga.com/}ReloadAccount
> has thrown exception, unwinding now
> java.lang.NullPointerException
> at
> org.apache.cxf.ws.rm.soap.RMSoapInterceptor.decodeHeaders(RMSoapInterceptor.java:286)
> at
> org.apache.cxf.ws.rm.soap.RMSoapInterceptor.unmarshalRMProperties(RMSoapInterceptor.java:249)
> at
> org.apache.cxf.ws.rm.soap.RMSoapInterceptor.decode(RMSoapInterceptor.java:234)
> at
> org.apache.cxf.ws.rm.soap.RMSoapInterceptor.mediate(RMSoapInterceptor.java:136)
> at
> org.apache.cxf.ws.rm.soap.RMSoapInterceptor.handleMessage(RMSoapInterceptor.java:124)
> at
> org.apache.cxf.ws.rm.soap.RMSoapInterceptor.handleMessage(RMSoapInterceptor.java:86)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:123)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:323)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:289)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:72)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:943)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:879)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
> at org.eclipse.jetty.server.Server.handle(Server.java:345)
> at
> org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)
> at
> org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:936)
> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:801)
> at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:224)
> at
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:51)
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:586)
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:44)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)
> at java.lang.Thread.run(Thread.java:662)
> This can probably be handled more gracefully?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
