You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/04/24 07:19:38 UTC
[jira] Created: (CAMEL-1562) Introduce Channel between each EIP in
the route path
Introduce Channel between each EIP in the route path
----------------------------------------------------
Key: CAMEL-1562
URL: https://issues.apache.org/activemq/browse/CAMEL-1562
Project: Apache Camel
Issue Type: New Feature
Components: camel-core
Affects Versions: 2.0-M1
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.0.0
We should introduce a org.apache.camel.Channel to act as delegate for routing an exchange to the next processor in the route graph.
The Channel should contain the logic to perform the needed work on the Exchange before it can be routed such as
- applying interceptors
- using the correct error handler
- and more to come in the future
The first phase of implementation will be to move the existing logic that wraps the processor in interceptors and error handlers from the ProcessorDefinition into the Channel.
So the Channel contains this logic.
Later we can introduce runtime behavior and much more.
I will start a discussion on it on the dev forum in a second.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (CAMEL-1562) Introduce Channel between each
EIP in the route path
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on CAMEL-1562 started by Claus Ibsen.
> Introduce Channel between each EIP in the route path
> ----------------------------------------------------
>
> Key: CAMEL-1562
> URL: https://issues.apache.org/activemq/browse/CAMEL-1562
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.0-M1
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> We should introduce a org.apache.camel.Channel to act as delegate for routing an exchange to the next processor in the route graph.
> The Channel should contain the logic to perform the needed work on the Exchange before it can be routed such as
> - applying interceptors
> - using the correct error handler
> - and more to come in the future
> The first phase of implementation will be to move the existing logic that wraps the processor in interceptors and error handlers from the ProcessorDefinition into the Channel.
> So the Channel contains this logic.
> Later we can introduce runtime behavior and much more.
> I will start a discussion on it on the dev forum in a second.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1562) Introduce Channel between each EIP in
the route path
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-1562.
--------------------------------
Resolution: Fixed
Added Navigate feature so we can navigate the routes (the ones with the processors) at runtime and thus also navigate and find all the Channels.
This allows us to tamper with the route at runtime. And opens up new possibilities with better tooling support and whatnot.
See the navigate method on the Route interface. And the NavigateRouteTest is just showing a simple in action of this.
trunk: 769303
> Introduce Channel between each EIP in the route path
> ----------------------------------------------------
>
> Key: CAMEL-1562
> URL: https://issues.apache.org/activemq/browse/CAMEL-1562
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.0-M1
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> We should introduce a org.apache.camel.Channel to act as delegate for routing an exchange to the next processor in the route graph.
> The Channel should contain the logic to perform the needed work on the Exchange before it can be routed such as
> - applying interceptors
> - using the correct error handler
> - and more to come in the future
> The first phase of implementation will be to move the existing logic that wraps the processor in interceptors and error handlers from the ProcessorDefinition into the Channel.
> So the Channel contains this logic.
> Later we can introduce runtime behavior and much more.
> I will start a discussion on it on the dev forum in a second.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1562) Introduce Channel between each EIP
in the route path
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51370#action_51370 ]
Claus Ibsen commented on CAMEL-1562:
------------------------------------
Discussion
http://www.nabble.com/-DISCUSS---Camel-2.0---Internal-API-reworkings----Channel-and--AsyncProcessor-td23210093.html
> Introduce Channel between each EIP in the route path
> ----------------------------------------------------
>
> Key: CAMEL-1562
> URL: https://issues.apache.org/activemq/browse/CAMEL-1562
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.0-M1
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> We should introduce a org.apache.camel.Channel to act as delegate for routing an exchange to the next processor in the route graph.
> The Channel should contain the logic to perform the needed work on the Exchange before it can be routed such as
> - applying interceptors
> - using the correct error handler
> - and more to come in the future
> The first phase of implementation will be to move the existing logic that wraps the processor in interceptors and error handlers from the ProcessorDefinition into the Channel.
> So the Channel contains this logic.
> Later we can introduce runtime behavior and much more.
> I will start a discussion on it on the dev forum in a second.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1562) Introduce Channel between each EIP
in the route path
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51369#action_51369 ]
Claus Ibsen commented on CAMEL-1562:
------------------------------------
First cut: 768186
> Introduce Channel between each EIP in the route path
> ----------------------------------------------------
>
> Key: CAMEL-1562
> URL: https://issues.apache.org/activemq/browse/CAMEL-1562
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.0-M1
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> We should introduce a org.apache.camel.Channel to act as delegate for routing an exchange to the next processor in the route graph.
> The Channel should contain the logic to perform the needed work on the Exchange before it can be routed such as
> - applying interceptors
> - using the correct error handler
> - and more to come in the future
> The first phase of implementation will be to move the existing logic that wraps the processor in interceptors and error handlers from the ProcessorDefinition into the Channel.
> So the Channel contains this logic.
> Later we can introduce runtime behavior and much more.
> I will start a discussion on it on the dev forum in a second.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.