+1 To aim for spec compliant URIs in camel 3. We should not try to
achieve this at all costs though. So if there are hard cases where we
would loose features we should discuss them in detail.
For properties the question is if they should be compliant URIs before
or after the replacement. Probably it is ok if they are only URIs after
the replacement.
Christian
Am 20.06.2012 02:37, schrieb Hadrian Zbarcea:
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.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
