Re: Patterns for DRY Camel endpoints

2015-02-05 Thread Nathan Jones
cause I want new routes to go through a standard build/deploy/test pipeline. -----Ursprüngliche Nachricht- Von: Nathan Jones [mailto:nat...@ncjones.com] Gesendet: Mittwoch, 4. Februar 2015 10:55 An: users@camel.apache.org Betreff: Patterns for DRY Camel endpoints Is there a standard pattern for defining Camel endpoints so that commonly used endpoint settings do not need to be repeated in every endpoint definition?

Re: Patterns for DRY Camel endpoints

2015-02-05 Thread Claus Ibsen
an > > >> -Ursprüngliche Nachricht- >> Von: Nathan Jones [mailto:nat...@ncjones.com] >> Gesendet: Mittwoch, 4. Februar 2015 10:55 >> An: users@camel.apache.org >> Betreff: Patterns for DRY Camel endpoints >> >> Is there a standard pattern for def

AW: Patterns for DRY Camel endpoints

2015-02-04 Thread jhm
ng special builders sound also fine, but a lot of work as it requires one builder per endpoint ... Jan > -Ursprüngliche Nachricht- > Von: Nathan Jones [mailto:nat...@ncjones.com] > Gesendet: Mittwoch, 4. Februar 2015 10:55 > An: users@camel.apache.org > Betreff: Patterns for DR

Patterns for DRY Camel endpoints

2015-02-04 Thread Nathan Jones
Is there a standard pattern for defining Camel endpoints so that commonly used endpoint settings do not need to be repeated in every endpoint definition? For example, every RabbitMQ endpoint I declare always repeats the same connection settings like the following: rabbitmq://{{rabbitmq.host}}