Could you also explain to us the benefits in addition to the impacts ? On Thu, Jun 21, 2012 at 8:29 PM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: > Vote canceled. The community needs more time to understand the impacts. The > consensus is that current users of camel 2.x must not be impacted by this > change. > > > Hadrian > > > On 06/19/2012 08:37 PM, Hadrian Zbarcea wrote: >> >> Using URIs to identify and configure Endpoints is a notable Apache Camel >> innovation. This feature was present in Camel from its first release. >> The definition of the URIs syntax in unambiguous and defined in RFC-2396 >> [1]. >> >> Some components introduced along the way do not use valid URIs and this >> needs to be corrected. This vote is intended to formalize the apparent >> lazy consensus in the [discuss] thread [2] on the dev@ list. This vote >> reflects agreement with the principle only. If this vote passes the >> details of the solution will be fleshed out later. >> >> >> [ ] +1 Camel MUST use valid URIs for Endpoint configuration >> [ ] -1 Camel does not need to use valid URIs (please provide reason). >> >> Vote is open for at least 72 hours. >> >> >
-- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ FuseSource, Integration everywhere http://fusesource.com
