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.ji...@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 >
