You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Aki Yoshida (Updated) (JIRA)" <ji...@apache.org> on 2012/04/20 12:14:42 UTC
[jira] [Updated] (CXF-4249) Add to RMTxStore configuration options
for schema name and datasource
[ https://issues.apache.org/jira/browse/CXF-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aki Yoshida updated CXF-4249:
-----------------------------
Description:
Make the current schema name of RMTxStore to be configurable per RMTxStore instance so that one can use the same database to host multiple overlapping scenarios or in other words, to host groups of scenarios in isolation (e.g., for multiple tenants).
Basically, the idea is to add property schenaName. When it is set, it is used to set the current schema to this specific schema. If unset, it uses the default.
Additionally, add method setDataSource to make it easier to configure the store using a DataSource.
was:
Make the current schema name of RMTxStore to be configurable per RMTxStore instance so that one can use the same database to host multiple overlapping scenarios or in other words, to host groups of scenarios in isolation (e.g., for multiple tenants).
Basically, the idea is to add property schenaName. When it is set, it is used to set the current schema to this specific schema. If unset, it uses the default.
Summary: Add to RMTxStore configuration options for schema name and datasource (was: Make RMTxStore's current schema name to be configurable)
> Add to RMTxStore configuration options for schema name and datasource
> ---------------------------------------------------------------------
>
> Key: CXF-4249
> URL: https://issues.apache.org/jira/browse/CXF-4249
> Project: CXF
> Issue Type: Improvement
> Components: WS-* Components
> Reporter: Aki Yoshida
> Assignee: Aki Yoshida
> Priority: Minor
> Fix For: 2.6.1, 2.5.4
>
>
> Make the current schema name of RMTxStore to be configurable per RMTxStore instance so that one can use the same database to host multiple overlapping scenarios or in other words, to host groups of scenarios in isolation (e.g., for multiple tenants).
> Basically, the idea is to add property schenaName. When it is set, it is used to set the current schema to this specific schema. If unset, it uses the default.
> Additionally, add method setDataSource to make it easier to configure the store using a DataSource.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira