directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (DIRRMS-97) Remove the Oracle dependency in the JDBC module
Date Thu, 03 Jun 2004 17:04:53 GMT
The following comment has been added to this issue:

     Author: Alex Karasulu
    Created: Thu, 3 Jun 2004 10:03 AM
Perhaps the best way to handle this is to make the jdbc factories depend on DAO interfaces
rather than directly interfacing with a database.  This means implementing the DAO object
interfaces for Oracle in a separate project.

The jdbc rms provider can then load the right DAO implementation based on the jdbc-driver
setting.  Basically we're going to need a DAO factory to instantiate the right set of DAO
objects for the specific database. It's probably best if this occurs in a separate branch
of RMS.

So to summarize the following actions will need to be taken:

o branch rms off of trunk
o creation of a new jdbc-oracle maven project
o create intermediate DAO stubs
o create DAOFactory 
o refactor jdbc project's RMS factory impls to use DAO interfaces  
o implement DAO objects to go against oracle in jdbc-oracle

View this comment:

View the issue:

Here is an overview of the issue:
        Key: DIRRMS-97
    Summary: Remove the Oracle dependency in the JDBC module
       Type: Improvement

     Status: Open
   Priority: Critical

    Project: Directory RMS

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Tue, 25 May 2004 12:37 AM
    Updated: Thu, 3 Jun 2004 10:03 AM

We need to separate out the Oracle code into another module all together.  We cannot keep
it here in the jdbc provider's implementation.  Plus we definately need to support an open
source database as well.  Two candidates come to mind off the bat: postgres SQL and HSQLDB.
 PostgresSQL is the open source Oracle and HSQLDB is an embeddable Java database so its great
for platform independent testing.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message