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/09 11:11:35 UTC
[jira] Created: (CAMEL-1525) seda component - the exchange copied
should not use the UoW from the source
seda component - the exchange copied should not use the UoW from the source
---------------------------------------------------------------------------
Key: CAMEL-1525
URL: https://issues.apache.org/activemq/browse/CAMEL-1525
Project: Apache Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.0-M1, 1.6.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.0.0, 1.6.1
The async endpoints such as seda and wireTap should not share the same UnitOfWork as the source.
They are a total new independent exchange and should have their own UnitOfWork.
See nabble
http://www.nabble.com/UnitOfWork-ends-too-soon-with-Seda-endpoints-td22950359.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1525) seda component - the exchange copied
should not use the UoW from the source
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-1525.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.6.1)
Fixed on 2.0 only as there is an API change and the issue is not serious. The UoW is scheduled for an overhaul in Camel 2.1
trunk: 763886
> seda component - the exchange copied should not use the UoW from the source
> ---------------------------------------------------------------------------
>
> Key: CAMEL-1525
> URL: https://issues.apache.org/activemq/browse/CAMEL-1525
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 1.6.0, 2.0-M1
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> The async endpoints such as seda and wireTap should not share the same UnitOfWork as the source.
> They are a total new independent exchange and should have their own UnitOfWork.
> See nabble
> http://www.nabble.com/UnitOfWork-ends-too-soon-with-Seda-endpoints-td22950359.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.