You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Roman Kalukiewicz (JIRA)" <ji...@apache.org> on 2008/04/02 13:12:32 UTC
[jira] Created: (CAMEL-426) splitter() should have the same
parallel processing functionality that multicast() has
splitter() should have the same parallel processing functionality that multicast() has
--------------------------------------------------------------------------------------
Key: CAMEL-426
URL: https://issues.apache.org/activemq/browse/CAMEL-426
Project: Apache Camel
Issue Type: Improvement
Components: camel-core
Reporter: Roman Kalukiewicz
Assignee: Roman Kalukiewicz
Ability to have
{code}
from("direct:parallel").splitter(body().tokenize(","), true).to("mock:result");
{code}
where {{true}} parameter to splitter should behave like in {{multicast()}} --- processing is done in separate threads for each 'part'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-426) splitter() should have the same
parallel processing functionality that multicast() has
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-426:
------------------------------
Fix Version/s: 1.4.0
Affects Version/s: 1.4.0
Its fixed in Camel 1.4 actually.
> splitter() should have the same parallel processing functionality that multicast() has
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-426
> URL: https://issues.apache.org/activemq/browse/CAMEL-426
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.4.0
> Reporter: Roman Kalukiewicz
> Assignee: Roman Kalukiewicz
> Fix For: 1.4.0
>
>
> Ability to have
> {code}
> from("direct:parallel").splitter(body().tokenize(","), true).to("mock:result");
> {code}
> where {{true}} parameter to splitter should behave like in {{multicast()}} --- processing is done in separate threads for each 'part'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-426) splitter() should have the same
parallel processing functionality that multicast() has
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41974#action_41974 ]
Claus Ibsen commented on CAMEL-426:
-----------------------------------
Roman, remember to update the wiki with the new "true" parameter. We need the wiki documentation to shine and that users will be able to see what features and options Camel really has.
> splitter() should have the same parallel processing functionality that multicast() has
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-426
> URL: https://issues.apache.org/activemq/browse/CAMEL-426
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Roman Kalukiewicz
> Assignee: Roman Kalukiewicz
>
> Ability to have
> {code}
> from("direct:parallel").splitter(body().tokenize(","), true).to("mock:result");
> {code}
> where {{true}} parameter to splitter should behave like in {{multicast()}} --- processing is done in separate threads for each 'part'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-426) splitter() should have the same
parallel processing functionality that multicast() has
Posted by "Roman Kalukiewicz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Kalukiewicz resolved CAMEL-426.
-------------------------------------
Resolution: Fixed
Functionality added by refactoring {{MulticastProcessor}}
> splitter() should have the same parallel processing functionality that multicast() has
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-426
> URL: https://issues.apache.org/activemq/browse/CAMEL-426
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Roman Kalukiewicz
> Assignee: Roman Kalukiewicz
>
> Ability to have
> {code}
> from("direct:parallel").splitter(body().tokenize(","), true).to("mock:result");
> {code}
> where {{true}} parameter to splitter should behave like in {{multicast()}} --- processing is done in separate threads for each 'part'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.