You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Aki Yoshida (JIRA)" <ji...@apache.org> on 2013/02/14 18:22:13 UTC
[jira] [Resolved] (CXF-4812) NPE on MessageModeInInterceptor when
sending empty SOAPBody
[ https://issues.apache.org/jira/browse/CXF-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aki Yoshida resolved CXF-4812.
------------------------------
Resolution: Fixed
Fix Version/s: 2.5.10
2.6.7
2.7.4
2.8.0
http://svn.apache.org/viewvc?view=revision&revision=r1444251
> NPE on MessageModeInInterceptor when sending empty SOAPBody
> -----------------------------------------------------------
>
> Key: CXF-4812
> URL: https://issues.apache.org/jira/browse/CXF-4812
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime, Soap Binding
> Affects Versions: 2.7.0
> Environment: Tested on Eclipse IDE environment on a maven-based project.
> CXF version is 2.7.0
> Java is JDK1.6.0_37
> Reporter: Jesus CASTILLO
> Assignee: Aki Yoshida
> Fix For: 2.8.0, 2.7.4, 2.6.7, 2.5.10
>
>
> I'm getting a NPE on MessageModeInInterceptor when sending a SOAP message with empty body. In addition, no WSDL and using JAX-WS Dispatch API and Provider interface with SOAPMessage.
> Everything is fine if the SOAPBody contains a payload but it fails when is empty. This is the stack trace.
> java.lang.NullPointerException
> at org.apache.cxf.jaxws.interceptors.MessageModeInInterceptor.handleMessage(MessageModeInInterceptor.java:71)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:354)
> at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:318)
> at org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:72)
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1074)
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1010)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
> at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
> at org.eclipse.jetty.server.Server.handle(Server.java:361)
> at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:485)
> at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:937)
> at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:998)
> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:856)
> at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
> at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
> at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:627)
> at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:51)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
> at java.lang.Thread.run(Thread.java:662)
> and that line in the interceptor is:
> public void handleMessage(Message message) throws Fault {
> if (!bindingName.equals(message.getExchange().get(BindingOperationInfo.class)
> .getBinding().getName())) {
> It seems that the BindingOperationInfo is not found in the exchange.
> This is the Test scenario:
> 1. Tested on CXF 2.7.0
> 2. NO WSDL. It's pure SOAP messaging.
> 3. Soap 1.2 Binding although tested with 1.1. and is the same error.
> 4. Client side using JAX-WS Dispatch API with SOAPMessage.
> 5. Server side using JAX-WS Provider interface with SOAPMessage.
> Rgds,
> Jesus.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira