portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joachim Müller (JIRA) <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-809) Add table schema aware datasource proxy
Date Fri, 23 Nov 2007 20:59:43 GMT

    [ https://issues.apache.org/jira/browse/JS2-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545128

Joachim Müller commented on JS2-809:

The usage of the TransactionAwareDataSourceProxy is an artifact from the source of the idea
(http://forum.springframework.org/showthread.php?t=10728). There, it is required to change
the database schema within a local transaction, so the getConnection() method must be transaction

Since this functionality is stripped in my patch, and probably is not needed here, the SchemaAwareDataSourceProxy
could extend from BasicDataSource I guess.

The fragment in the spring configuration (property maxRetriedStarts in /src/webapp/WEB-INF/assembly)
is my mistake. I created the patch against an already patched version of the assembly file.
Sorry about this, the two issues are not related at all!

I will test the SchemaAwareDataSourceProxy extending from BasicDataSource and repost patches
against the current trunk as soon as I have some spare time.

> Add table schema aware datasource proxy
> ---------------------------------------
>                 Key: JS2-809
>                 URL: https://issues.apache.org/jira/browse/JS2-809
>             Project: Jetspeed 2
>          Issue Type: New Feature
>          Components: Persistence and DAO
>    Affects Versions: 2.1, 2.1.2, 2.1.3, 2.2
>            Reporter: Joachim Müller
>             Fix For: 2.1.3, 2.2
>         Attachments: patch.diff
> In some environments (DB2, Oracle, PostGres) the table schema may be not equally associated
with the user name, provided in the jdbc connection parameters. At the moment it is not possible
to set the table schema used for the db connections.
> This table schema aware datasource proxy optionally injects a schema selection sql statement
into an existing database connection. It proxies a DataSource and executes an injected sql
statement on every getConnection() call.
> The proxy can be configured via the spring configurations files and therefore allows
to add table schema support to the import functionality only. This might come in handy if
you have to import into a certain table schema and cannot rely on the web application container
datasource configuration that might already support table schemas (like websphere does).
> The solution was inspired from http://forum.springframework.org/showthread.php?t=10728,
although the runtime schema switching functionality was stripped.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message