[ 
https://issues.apache.org/jira/browse/JCS-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vishal Sinha updated JCS-48:
----------------------------

    Attachment: JCSDataSourceHelper.java
                JDBCDiskCache.java

I have added one class JCSDataSourceHelper and modified the existing class 
JDBCDiskCache. I have tried to keep it as low risk, and jcs code will behave as 
it used to do if we revert back to old configuration in cache.ccf. 

For the datasource to work, the only change required in cache.ccf is: 
jcs.auxiliary.JDBC.attributes.url=jdbc/jcsDataSource
that is, specify datasource jndi instead of DB url 

But I do have the dependency in the code that datasource jndi name should start 
with "jdbc/" just to identify thats its datasource jndi name and not the DB url.

Regards
Vishal Sinha


> JDBC Disk Auxiliary Cache Configuration -> support JNDI datasource in 
> Appservers
> --------------------------------------------------------------------------------
>
>                 Key: JCS-48
>                 URL: https://issues.apache.org/jira/browse/JCS-48
>             Project: JCS
>          Issue Type: Improvement
>          Components: JDBC Disk Cache
>    Affects Versions: jcs-1.4-dev
>            Reporter: hanasaki jiji
>            Assignee: Aaron Smuts
>            Priority: Minor
>         Attachments: JCSDataSourceHelper.java, JDBCDiskCache.java
>
>
> JDBC Disk Auxiliary Cache Configuration -> support JNDI datasource in 
> Appservers
> http://jakarta.apache.org/jcs/JDBCDiskCacheProperties.html
> Allow property "url" to be used (or add URI) so that tomcat and other 
> appservers providing JNDI datasources can be used to specific the table and 
> id/pass and connection information.  In this case several other properties 
> would be ignored: tableName, userName, password.

-- 
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to