Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of dcheckoway@gmail.com
 designates 209.85.213.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=DC02YD+BGMvNtb+pKswEcLppQCo2t6BO+mYGgFk2xtZK3gogDyh2mW6oHOVLxSANRJ
         ktk4xY4nCIeYgH1lk3gi80f1/mS+K5r4a/bQSxqA07Kc4Cd7gxLtoanMJ2nvS9c+1jeP
         D1NUYQ85Gr0G/GlyTyNLKqd9iy575Yqh9ggvI=
MIME-Version: 1.0
In-Reply-To: <4D282351.1000601@gmail.com>
References: <1294429615923-3332393.post@n5.nabble.com>
	<4D282351.1000601@gmail.com>
Date: Sat, 8 Jan 2011 04:25:23 -0500
Message-ID: <AANLkTikB6r8EX556VqChf_ACkX1nE9ZgNhRY9VL3w2WD@mail.gmail.com>
Subject: Re: Camel-http and multiple Set-Cookie headers
From: Dan Checkoway <dcheckoway@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=0023547c91f77d15f90499525078

--0023547c91f77d15f90499525078
Content-Type: text/plain; charset=ISO-8859-1

How about this?

http://commons.apache.org/collections/apidocs/org/apache/commons/collections/map/MultiValueMap.html

That still implements Map, so users theoretically wouldn't have to change
anything, or change much.  And those who need to grab Set-Cookie headers
could use .getCollection() to access them all.

Dan

On Sat, Jan 8, 2011 at 3:41 AM, Willem Jiang <willem.jiang@gmail.com> wrote:

> Camel message header is a map, so if there are more than one value with
> same key set into the header, you can see only one entry in the message
> header.
> Maybe we need to find other way to work around it in camel-http component.
>
>
> On 1/8/11 3:46 AM, lauri wrote:
>
>>
>> Hi,
>>
>> I'm using Camel to integrate service A to service B using camel-http.
>> Service B is just an external web server that needs to set some cookies
>> once
>> in a while. However, if multiple Set-Cookie headers are present in B's
>> responses, I'm only able to read one of them on A. The reason for this is
>> that org.apache.camel.Message seems to only have methods for handling
>> headers that can exist only once.
>>
>> So, have I completely misunderstood something here or is this just some
>> kind
>> of a limitation of camel-http module?
>>
>> Best,
>> Lauri
>>
>
>
> --
> Willem
> ----------------------------------
> FuseSource
> Web: http://www.fusesource.com
> Blog:    http://willemjiang.blogspot.com (English)
>         http://jnn.javaeye.com (Chinese)
> Twitter: willemjiang
>

--0023547c91f77d15f90499525078--