camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hiram Chirino <>
Subject Re: [VOTE] Camel MUST use valid URIs for identifying and configuring Endpoints
Date Thu, 21 Jun 2012 16:41:48 GMT
-1 This change would NOT be transparent to 2.x users.  Lets not hurt our
2.x Camel community! This should have been a discussion about how we could
improve Camel 3.x.

>From my point of view, Camel is all about being flexible and an integrating
as many technologies as possible and avoid exclusive of approaches.  I
think that needs to continue even in how you configure endpoints.  You
might be able to convince me that most camel components SHOULD validate
their endpoint config uri using the Java URI class.  Or that components
should have a more formal way of expressing what endpoint config syntax it

java.lang.String is the most flexible and OPEN configuration java class we
have.  Lets keep it that way.

On Tue, Jun 19, 2012 at 8: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.
> --
> Hadrian Zbarcea
> Principal Software Architect
> Talend, Inc
> [1]**rfc2396.txt<>
> [2] http://mail-archives.apache.**org/mod_mbox/camel-dev/201206.**
> mbox/%3C4FD60168.5090009%**<>



*Hiram Chirino*

*Software Fellow | FuseSource Corp.*

* |*

*skype: hiramchirino | twitter: @hiramchirino<>

*blog: Hiram Chirino's Bit Mojo <>*



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message