[
https://issues.apache.org/jira/browse/CAMEL-12608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529759#comment-16529759
]
Zoran Regvart commented on CAMEL-12608:
---------------------------------------
One issue I can see is that _if_ we can only guarantee that by the point we
reach the {{configure}} method that the required initialization is performed
(i.e. not before), this approach will fail. This is probably not the case, i.e.
we can add to RouteBuilder at any point not just when the {{configure}} is
invoked, but it would lock us out of proscribing that lifecycle.
> Add default no-op implementation of RouteBuilder
> ------------------------------------------------
>
> Key: CAMEL-12608
> URL: https://issues.apache.org/jira/browse/CAMEL-12608
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Roland Huss
> Priority: Major
>
> Inspired by JMockit which use object initializers for introducing their Java
> DSL, I think it would be a good idea to add a no-op default implementation of
> RouteBuilder, with a short name like 'Routes'.
> {code:java}
> ctx.add(new Routes {{
> from("file:data/inbox?noop=true")
> .to("file:data/outbox");
> }});
> {code}
> That way one can avoid the creation of anonymous inner classes, which is not
> only shorted and less boilerplate but also creates less classes and saves
> non-heap memory.
>
> A simple POC as submitted as PR at
> [https://github.com/apache/camel/pull/2401] which could be extended to
> include better unit testing and documentation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
