On Fri, Oct 16, 2009 at 5:52 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Fri, Oct 16, 2009 at 1:52 AM, chrajanirao <rajan...@gmail.com> wrote: >> >> We upgraded from Camel 1.5 to 2.0 and realized that the default behavior of >> RecipientList has changed. Even though in 2.0, we can specify a delimiter, >> comma is always considered as a delimiter on top of what ever we specified >> as our custom delimiter. >> > > Could you create a ticket for that?
I created a ticket https://issues.apache.org/activemq/browse/CAMEL-2070 And is working on a fix right now. > So for example you can specify # as delimiter and then comma is not > considered. > > >> Is there a way to make it ignore commas in the values in Camel 2.0? If not, >> I don't think its a good idea to hard code that additional comma delimiter >> no matter what. If someone wants comma as delimiter, they can specify it in >> provided "delimiter" attribute/tokenizer. >> >> Thanks, >> Rajani. >> -- >> View this message in context: >> http://www.nabble.com/Dynamic-RecipientList-delimeter-issue-tp25917854p25917854.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> >> > > > > -- > Claus Ibsen > Apache Camel Committer > > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
