Thoughts on supporting JNDI based Oracle file system/persistence manager
implementations
----------------------------------------------------------------------------------------
Key: JCR-942
URL: https://issues.apache.org/jira/browse/JCR-942
Project: Jackrabbit
Issue Type: Improvement
Components: core
Affects Versions: 1.3
Environment: Oracle 10g
Reporter: Hemanta Gupta
Priority: Minor
This may not be relevant for too many people, but I faced a situation where I
couldn't use the stock Oracle file system and persistence manager
implementations since we couldn't place the clear text DB password in
repository.xml (for security reasons).
I tried adapting the classes to use a data-source instead, but this didn't work
out immediately because of the Oracle specific blob handling being performed by
these classes. They expect the connection to be the original native connection
returned by the driver, so in the case of wrapped connections returned by
managed data-sources, a ClassCastException is thrown by
oracle.sql.BLOB.createTemporary().
I finally got things working thanks to the fact that both application servers
we support (JBoss and WebLogic) allow extraction of the native connection from
a wrapped managed connection. Spring's NativeJdbcExtractor interface proved
very helpful here; I simply used the right implementation for extracting the
native connection and using it wherever I thought it was required (modified
code to be attached later).
So to sum up, would it be possible for JR to provide this kind of functionality
out-of-the-box? To be specific, could you provide JNDI based Oracle file system
and persistence manager implementations where we can plug in some kind of
native connection extractor, and have the implementations internally use the
native connection for Oracle specific stuff?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
