camel will try to digest the HttpServletRequest and setup the message headers
and body.
It's a common practice to consume the input stream from message body :)
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http:/
This is resolved by using/parsing the input stream from camel body instead of
using the HttpServletRequest from camel Headers.
--
View this message in context:
http://camel.465427.n5.nabble.com/Using-camel-servlet-with-Multipart-unable-to-fetch-the-file-tp5732204p5732534.html
Sent from the Came
I'm using the OSGI service for camel servlet and I do not want to use
camel-jetty as it takes its own port instead of existing jetty server port.
What strange is I can see the contents of the multipart data from request if
I parse them manually, But I am unable to separate the form fields and file
camel-jetty is using org.eclipse.jetty.servlets.MultiPartFilter to handle this
multipart message.
You may consider to configure the filter in your web.xml.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://wille
Thank you for replying! I have tried removing them but no difference. Am I
using the component correctly? Is there any other way to get the form fields
and data separetely? I have tried camel-jetty component and it separates the
form fields and data, Is there anything similar to that in camel-servl
Hi
I suggest you remove the streamCaching() and to("log:servlet") from your route.
Current streamCaching doesn't support to caching the Servlet request input
stream.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog:
