You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Brian DePradine (JIRA)" <ji...@apache.org> on 2010/03/16 18:44:27 UTC
[jira] Created: (ARIES-256) Modify the transaction wrappers bundle
to use a service tracker instead of blueprint
Modify the transaction wrappers bundle to use a service tracker instead of blueprint
------------------------------------------------------------------------------------
Key: ARIES-256
URL: https://issues.apache.org/jira/browse/ARIES-256
Project: Aries
Issue Type: Improvement
Components: Transaction
Reporter: Brian DePradine
Currently the transaction wrappers bundle uses a reference in blueprint to retrieve an XADataSources that it can wrap for transaction enlistment. The wrapped XADataSource is then re-exported as a DataSource with a fixed propery. This is better done using a bundle activator as it would allow us to reuse any properties defined on the XADataSource with the new wrapped DataSource.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ARIES-256) Modify the transaction wrappers bundle
to use a service tracker instead of blueprint
Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alasdair Nottingham reassigned ARIES-256:
-----------------------------------------
Assignee: Alasdair Nottingham
> Modify the transaction wrappers bundle to use a service tracker instead of blueprint
> ------------------------------------------------------------------------------------
>
> Key: ARIES-256
> URL: https://issues.apache.org/jira/browse/ARIES-256
> Project: Aries
> Issue Type: Improvement
> Components: Transaction
> Reporter: Brian DePradine
> Assignee: Alasdair Nottingham
> Attachments: patch.txt
>
>
> Currently the transaction wrappers bundle uses a reference in blueprint to retrieve an XADataSources that it can wrap for transaction enlistment. The wrapped XADataSource is then re-exported as a DataSource with a fixed propery. This is better done using a bundle activator as it would allow us to reuse any properties defined on the XADataSource with the new wrapped DataSource.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ARIES-256) Modify the transaction wrappers bundle
to use a service tracker instead of blueprint
Posted by "Brian DePradine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian DePradine updated ARIES-256:
----------------------------------
Attachment: patch.txt
Attached a apatch to address this issue.
> Modify the transaction wrappers bundle to use a service tracker instead of blueprint
> ------------------------------------------------------------------------------------
>
> Key: ARIES-256
> URL: https://issues.apache.org/jira/browse/ARIES-256
> Project: Aries
> Issue Type: Improvement
> Components: Transaction
> Reporter: Brian DePradine
> Attachments: patch.txt
>
>
> Currently the transaction wrappers bundle uses a reference in blueprint to retrieve an XADataSources that it can wrap for transaction enlistment. The wrapped XADataSource is then re-exported as a DataSource with a fixed propery. This is better done using a bundle activator as it would allow us to reuse any properties defined on the XADataSource with the new wrapped DataSource.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (ARIES-256) Modify the transaction wrappers
bundle to use a service tracker instead of blueprint
Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on ARIES-256 started by Alasdair Nottingham.
> Modify the transaction wrappers bundle to use a service tracker instead of blueprint
> ------------------------------------------------------------------------------------
>
> Key: ARIES-256
> URL: https://issues.apache.org/jira/browse/ARIES-256
> Project: Aries
> Issue Type: Improvement
> Components: Transaction
> Reporter: Brian DePradine
> Assignee: Alasdair Nottingham
> Attachments: patch.txt
>
>
> Currently the transaction wrappers bundle uses a reference in blueprint to retrieve an XADataSources that it can wrap for transaction enlistment. The wrapped XADataSource is then re-exported as a DataSource with a fixed propery. This is better done using a bundle activator as it would allow us to reuse any properties defined on the XADataSource with the new wrapped DataSource.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ARIES-256) Modify the transaction wrappers bundle
to use a service tracker instead of blueprint
Posted by "Brian DePradine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian DePradine resolved ARIES-256.
-----------------------------------
Resolution: Fixed
> Modify the transaction wrappers bundle to use a service tracker instead of blueprint
> ------------------------------------------------------------------------------------
>
> Key: ARIES-256
> URL: https://issues.apache.org/jira/browse/ARIES-256
> Project: Aries
> Issue Type: Improvement
> Components: Transaction
> Reporter: Brian DePradine
> Assignee: Alasdair Nottingham
> Attachments: patch.txt
>
>
> Currently the transaction wrappers bundle uses a reference in blueprint to retrieve an XADataSources that it can wrap for transaction enlistment. The wrapped XADataSource is then re-exported as a DataSource with a fixed propery. This is better done using a bundle activator as it would allow us to reuse any properties defined on the XADataSource with the new wrapped DataSource.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.