No transformers for HttpServletRequest to InputStream (and others?)

Details

  • User impact:
    Medium
  • Effort points:
    0.5
  • Similar Issues:
    None

Description

I'm getting this exception when using the MuleReceiverServlet with CXF. This works fine when the regular HTTP transport is being used:

[01-22 13:56:55] WARN CxfServiceComponent [SocketListener0-1]: Could not dispatch message to XFire!
org.mule.umo.transformer.TransformerException: Could not find a transformer to transform "org.mortbay.jetty.servlet.ServletHttpRequest" to "java.io.InputStream".
at org.mule.impl.registry.AbstractRegistry.lookupTransformer(AbstractRegistry.java:276)
at org.mule.impl.MuleMessage.getPayload(MuleMessage.java:162)
at org.mule.impl.MuleMessage.getPayload(MuleMessage.java:120)
at org.mule.impl.MuleEvent.transformMessage(MuleEvent.java:320)
at org.mule.impl.MuleEventContext.transformMessage(MuleEventContext.java:112)
at org.mule.providers.cxf.CxfServiceComponent.sendToDestination(CxfServiceComponent.java:193)
at org.mule.providers.cxf.CxfServiceComponent.onCall(CxfServiceComponent.java:110)
at org.mule.impl.model.resolvers.CallableEntryPointResolver.invoke(CallableEntryPointResolver.java:52)
at org.mule.impl.model.resolvers.DefaultEntryPointResolverSet.invoke(DefaultEntryPointResolverSet.java:50)
at org.mule.impl.DefaultLifecycleAdapter.intercept(DefaultLifecycleAdapter.java:189)
at org.mule.impl.model.DefaultMuleProxy.onCall(DefaultMuleProxy.java:193)
at org.mule.impl.model.seda.SedaComponent.doSend(SedaComponent.java:242)
at org.mule.impl.model.AbstractComponent.sendEvent(AbstractComponent.java:505)
at org.mule.impl.MuleSession.sendEvent(MuleSession.java:343)
at org.mule.routing.inbound.InboundRouterCollection.send(InboundRouterCollection.java:210)
at org.mule.routing.inbound.InboundRouterCollection.route(InboundRouterCollection.java:177)
at org.mule.providers.AbstractMessageReceiver$DefaultInternalMessageListener.onMessage(AbstractMessageReceiver.java:600)
at org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:344)
at org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:267)
at org.mule.providers.http.servlet.MuleReceiverServlet.doGet(MuleReceiverServlet.java:115)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at org.mortbay.jetty.servlet.ServletHandler.dispatch(ServletHandler.java:677)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

See WsdlCallTestCase.testRequestWsdlWithServlets for more info.

Issue Links

relates to

Improvement - An improvement or enhancement to an existing feature or task. MULE-3234 Not all message filters and routers support streams

  • Critical - Crashes, loss of data, severe memory leak.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Perepelytsya added a comment -

Dan, I think we never supported http streaming. Not that it's not possible for this particular case, though.

Show
Andrew Perepelytsya added a comment - Dan, I think we never supported http streaming. Not that it's not possible for this particular case, though.
Hide
Permalink
Dan Diephouse added a comment -

Eh? This isn't really that hard of a bug to fix now that I look more closely. Someone just needs to change the HttpRequestToByteArray to actually extract an InputStream, OutputHandler, etc. It could probably just wrap InputStreamToObjectTransformer even.

Show
Dan Diephouse added a comment - Eh? This isn't really that hard of a bug to fix now that I look more closely. Someone just needs to change the HttpRequestToByteArray to actually extract an InputStream, OutputHandler, etc. It could probably just wrap InputStreamToObjectTransformer even.
Hide
Permalink
Dan Diephouse added a comment -

This was fixed when I switched the default return type of HttpRequestMessageAdapter.getPayload() to an InputStream.

Show
Dan Diephouse added a comment - This was fixed when I switched the default return type of HttpRequestMessageAdapter.getPayload() to an InputStream.

People

  • Assignee:
    Unassigned
    Reporter:
    Dan Diephouse
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: