Hi Fernando,

Thanks a lot. I will register and vote for the issue soon.

Best Regards,
Sergey Zhemzhitsky
Information Technology Division
Troika Dialog, 4, Romanov lane, Moscow 125009, Russia
Phone. +7 495 2580500 ext. 1246


-----Original Message-----
From: Fernando Ribeiro [mailto:[email protected]] 
Sent: Tuesday, May 17, 2011 11:17 PM
To: [email protected]
Subject: Re: Multiple headers with the same name

Sergey,

I think transforming to JMS-Property-Name-1, JMS-Property-Name-2,... is 
probably a better idea, and I've seen that in several products before.

The optimal solution, though, is improving JMS, and you may want to vote for 
http://java.net/jira/browse/JMS_SPEC-5, which I just opened.

Thanks,

Fernando

2011/5/17 Zhemzhitsky Sergey <[email protected]>

> Hi Claus,
>
> Thanks a lot. So for transports (for example jms) that do not support 
> complex headers like lists we have to invent something else, for 
> instance comma-separated header values?
>
> Best Regards,
> Sergey Zhemzhitsky
>
>
> -----Original Message-----
> From: Claus Ibsen [mailto:[email protected]]
> Sent: Tuesday, May 17, 2011 6:36 PM
> To: [email protected]
> Subject: Re: Multiple headers with the same name
>
> You can store multiple values as a List in the value for the header key.
>
>
> On Tue, May 17, 2011 at 4:29 PM, Zhemzhitsky Sergey < 
> [email protected]> wrote:
> > Hi there,
> >
> > Is it possible to have multiple exchange headers with the same name 
> > and
> different values like http request parameters or headers?
> >
> >
> > Best Regards,
> > Sergey Zhemzhitsky
> >
> >
> > _______________________________________________________
> >
> > The information contained in this message may be privileged and conf
> idential and protected from disclosure. If you are not the original 
> intended recipient, you are hereby notified that any review, 
> retransmission, dissemination, or other use of, or taking of any 
> action in reliance upon, this information is prohibited. If you have 
> received this communication in error, please notify the sender 
> immediately by replying to this message and delete it from your 
> computer. Thank you for your cooperation. Troika Dialog, Russia.
> > If you need assistance please contact our Contact Center  (+7495) 
> > 258
> > 0500 or go to www.troika.ru/eng/Contacts/system.wbp
> >
> >
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: [email protected]
> Web: http://fusesource.com
> CamelOne 2011: http://fusesource.com/camelone2011/
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
> _______________________________________________________
>
> The information contained in this message may be privileged and conf 
> idential and protected from disclosure. If you are not the original 
> intended recipient, you are hereby notified that any review, 
> retransmission, dissemination, or other use of, or taking of any 
> action in reliance upon, this information is prohibited. If you have 
> received this communication in error, please notify the sender 
> immediately by replying to this message and delete it from your 
> computer. Thank you for your cooperation. Troika Dialog, Russia.
> If you need assistance please contact our Contact Center  (+7495) 258 
> 0500 or go to www.troika.ru/eng/Contacts/system.wbp
>
>
>

_______________________________________________________

The information contained in this message may be privileged and conf idential 
and protected from disclosure. If you are not the original intended recipient, 
you are hereby notified that any review, retransmission, dissemination, or 
other use of, or taking of any action in reliance upon, this information is 
prohibited. If you have received this communication in error, please notify the 
sender immediately by replying to this message and delete it from your 
computer. Thank you for your cooperation. Troika Dialog, Russia. 
If you need assistance please contact our Contact Center  (+7495) 258 0500 or 
go to www.troika.ru/eng/Contacts/system.wbp  


Reply via email to