[
https://issues.apache.org/activemq/browse/CAMEL-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60462#action_60462
]
Hadrian Zbarcea commented on CAMEL-2914:
----------------------------------------
I have to update the wiki documentation tomorrow morning and then we can close
this issue.
A slightly better variation of this would be to modify the signature of the
wrap() method in PolicyDefinition itself and get rid of the
DefinitionAwarePolicy class. Now we have these 2 different iterfaces that both
represent policies that can inject code to be invoked during processing, but
the DefinitionAwarePolicy is also capable of altering the route. No need for
both, I think, the implementer of a Policy, could just ignore the last argument
if it has no need to alter the route. Although a binary incompatible change,
the migration is trivial.
I'll make this change tomorrow morning too, if there's no objection.
> 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
> 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.
