cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "EasternWahoo (JIRA)" <>
Subject [jira] Created: (CXF-2824) Error handling improvements for invalid Soap message content
Date Mon, 24 May 2010 15:46:26 GMT
Error handling improvements for invalid Soap message content

                 Key: CXF-2824
             Project: CXF
          Issue Type: Improvement
          Components: JAX-WS Runtime
    Affects Versions: 2.2.6
            Reporter: EasternWahoo

Soap web services clients may send garbage or invalid messages to our CXF jaxws web service.
 For example, the message may consist of a valid soap envelope, but the soap body is empty.
On other occasions, the soap body contains non-xml content.

CXF gets nullpointer exceptions in these cases, and returns a generic Soap fault, "Fault occurred
while processing".  Shouldn't the framework be able to provide a more useful message, such
as "malformed xml content", and not fail on a nullpointer exception?  

Below is a stack trace generated for a Soap Envelope containing an empty body:  

WARNING: Interceptor {}Hello_v1Servicehas thrown exception,
unwinding now
        at org.apache.cxf.frontend.SimpleMethodDispatcher.getMethod(
        at org.apache.cxf.service.invoker.AbstractInvoker.invoke(
        at org.apache.cxf.interceptor.ServiceInvokerInterceptor$
        at java.util.concurrent.Executors$ Source)
        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
        at Source)
        at org.apache.cxf.workqueue.SynchronousExecutor.execute(
        at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(
        at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
        at org.apache.cxf.transport.ChainInitiationObserver.onMessage(
        at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(
        at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(
        at org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(
        at org.mortbay.jetty.handler.ContextHandler.handle(
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
        at org.mortbay.jetty.handler.HandlerWrapper.handle(
        at org.mortbay.jetty.Server.handle(
        at org.mortbay.jetty.HttpConnection.handleRequest(
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(
        at org.mortbay.jetty.HttpParser.parseNext(
        at org.mortbay.jetty.HttpParser.parseAvailable(
        at org.mortbay.jetty.HttpConnection.handle(
        at org.mortbay.thread.QueuedThreadPool$

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message