camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Krasser (JIRA)" <>
Subject [jira] Commented: (CAMEL-209) Content Encrichment support
Date Thu, 12 Feb 2009 10:49:59 GMT


Martin Krasser commented on CAMEL-209:


wouldn't it be even better to resolve the resource endpoint in the EnricherType.doCreateProcessor()
method, create a producer from that endpoint and inject that producer into the Enricher?

public class EnricherType extends OutputType<EnricherType> {


  public Processor createProcessor(RouteContext routeContext) throws Exception {
      Enricher enricher = new Enricher(...);
      return enricher;


The Enricher then starts and stops the producer within its start()/stop() methods and uses
it in its process(Exchange) method to send the resourceExchange

public class Enricher extends ServiceSupport implements Processor {

   public void process(Exchange exchange) {

Then the enricher creation and wiring code has been moved to the EnricherType and the Enricher
is only doing the logic it needs to do.  What do you think?

I can provide a patch if you want.

> Content Encrichment support 
> ----------------------------
>                 Key: CAMEL-209
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Nicky Sandhu
>            Assignee: Jonathan Anstey
>             Fix For: 2.0.0
>         Attachments: camel-core.patch, camel-spring.patch
> ContentEnricher ( support
is needed. Here's a thread that outlines the usecase

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message