On Tue, Feb 9, 2010 at 2:03 AM, Pete Mueller <[email protected]> wrote:
> > Hello all, > > I am currently working with the camel-jetty integration for hosting some > web > services. During my implementation, I've found a few "oddities" that I > thought I would post here before opening actual bug reports. (NOTE: I am > using Camel 2.0) > > 1. When an exchange is create from a Jetty endpoint, the BodyType (as > reported via TraceInterceptor) is org.mortbay.jetty.HttpParser.Input. > Processing this data allows me to call getBody(String.class) to get the > POST > contents or getBody(HttpServletRequest.class) to get the request object. > However, this is only available to the first processor after the "from" > element. Subsequent processor calls to getBody(HttpServletRequest.class) > return null, which seem to be caused because the BodyType was translated > to > a InputStreamCache somewhere. I've tried various methods of passing the > message in to the message out, but I cannot avoid this conversion and loss > of request object. Is this intended behavior? If so, how do I get the > request object back? > I think you are describing the same problem I found; a fix went into 2.2-snapshot: https://issues.apache.org/activemq/browse/CAMEL-2386 Regards Wayne > Thanks for all your help. > -pete > -- > View this message in context: > http://old.nabble.com/Questions-about-camel-jetty-tp27509400p27509400.html > Sent from the Camel - Users mailing list archive at Nabble.com. > >
