The other three http producers (camel-ahc, camel-http, camel-http4) all transpose the Camel message body into the HTTP request body for any HTTP method. That behavior likely goes beyond what is necessary, but does not block using HTTP as expected. I do not think changes to those components are necessary for this issue.
On Thu, Oct 6, 2011 at 10:36 PM, Claus Ibsen (Commented) (JIRA) < j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/CAMEL-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122545#comment-13122545] > > Claus Ibsen commented on CAMEL-4521: > ------------------------------------ > > Could we check the other HTTP producers in > - camel-ahc > - camel-http > - camel-http4 > > If they have a similar issue? > > > camel-jetty should apply the Camel message body content as the HTTP > request body for HTTP PUT requests > > > ------------------------------------------------------------------------------------------------------ > > > > Key: CAMEL-4521 > > URL: https://issues.apache.org/jira/browse/CAMEL-4521 > > Project: Camel > > Issue Type: Improvement > > Components: camel-jetty > > Reporter: Rich Newcomb > > Assignee: David Valeri > > Priority: Minor > > Fix For: 2.9.0 > > > > Attachments: CAMEL-4521-camel-jetty-trunk.patch > > > > > > The camel-jetty JettyHttpProducer only transposes Camel message body > content into the HTTP request body if the HTTP method is POST. The > component should be updated to also attach body content when the HTTP PUT > method is specified. This will better support the expected HTTP method > semantics, and will allow camel-jetty to be used as a client for systems > that employ the "High REST" architecture paradigm. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators: > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa > For more information on JIRA, see: http://www.atlassian.com/software/jira > > >