Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <2036276.33991278476992178.JavaMail.jira@thor>
Date: Wed, 7 Jul 2010 00:29:52 -0400 (EDT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-2914) ProcessorDefinition aware Policy
In-Reply-To: <11876237.33631278444652364.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/CAMEL-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60465#action_60465 ] 

Claus Ibsen commented on CAMEL-2914:
------------------------------------

Damn we are still debating a solution on the mailing list. 

So please *don't* be so jumpy and apply patches so fast. I am not convinced this is the best solution right now.
Using policy to hack into the model is not the way to go.

Please discuss the proposal of a new SPI allowing to register a custom hook which can listen and react when the runtime processor model is created.
Then you can register the hook without using Policy or _polluting_ the routes.

> ProcessorDefinition aware Policy
> --------------------------------
>
>                 Key: CAMEL-2914
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2914
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Mark Proctor
>            Assignee: Hadrian Zbarcea
>             Fix For: 2.4.0
>
>         Attachments: DefinitionAwarePolicy.diff
>
>
> Currently a Policy cannot change the child processor definitions, and the processor instances are created prior to wrap being called. I would like to see the child Processsor defintions passed to wrap, and the processor instances created afterwards.
> As discussed in this mailing list post:
> http://camel.465427.n5.nabble.com/Using-Policy-to-alter-Definitions-before-building-tt696567.html#a696567

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