camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Taariq Levack <>
Subject Re: Problems with jetty component and posts with more then one value for a field.
Date Tue, 12 Jul 2011 05:33:19 GMT

I just tried it on 2.7.2 and you will see this kind of log.

[                          main] SpringCamelContext             TRACE
Getting endpoint with uri:
[                          main] SpringCamelContext             TRACE
Getting endpoint with normalized uri:
[                          main] DefaultComponent               DEBUG
Creating endpoint
path=[], parameters=[{say=hello, to=bill}]

Now I don't know if it's supposed to behave this way, or if it's
supposed to map such headers with an Object of type List or whatever.
But if you need a quick workaround, you can pass such a parameter
comma delimited and then split on that.
Assuming you're in control of the producer.


On Tue, Jul 12, 2011 at 7:13 AM, Claus Ibsen <> wrote:
> Hi
> What version of Camel are you using?
> On Tue, Jul 12, 2011 at 12:44 AM, Blair <> wrote:
>> I am wondering if i am doing this wrong, or if there is a work around?
>> Fields posted (or getted) from a form are placed as headers, which is a
>> wonderful beautiful thing.
>> however...
>> a url of the form http://localhost:8080/Message?say=hello&to=bob&to=bill
>> causes issues. The POST and PUT equivalents are the same.
>> The "to" header will only have bob, and bill is completely lost. I thought
>> we would end up with a list there, or something I could split on.
>> Anyway way around this?
>> The reason I want to to this is forms that have a list where you can select
>> multiple entries are sent this way, and I need to process the result.
>> --- Blair
>> --
>> View this message in context:
>> Sent from the Camel - Users mailing list archive at
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email:
> Web:
> Twitter: davsclaus, fusenews
> Blog:
> Author of Camel in Action:

View raw message