[ISSUES] Updated: (JLCP-166) Central DAOManager

The following issue has been updated:

    Updater: Matthew Schmidt (mailto:[email protected])
       Date: Fri, 2 May 2003 6:06 PM
    Comment:
Just too much had to happen this release, moving it to the next one.
    Changes:
          Fix Version changed from  to 0.7.0 (Shiva)
          Fix Version changed from 0.5.1 to 
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.jlcp.org/secure/ViewIssue.jspa?key=JLCP-166&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.jlcp.org/secure/ViewIssue.jspa?key=JLCP-166


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JLCP-166
    Summary: Central DAOManager
       Type: Improvement

     Status: Assigned
   Priority: Critical

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: Javalobby Community Platform
   Fix Fors:
             0.7.0 (Shiva)
   Versions:
             0.5.0 (Delorean)

   Assignee: J Aaron Farr
   Reporter: Matthew Schmidt

    Created: Wed, 9 Apr 2003 8:03 AM
    Updated: Fri, 2 May 2003 6:06 PM

Description:
It would be great to have a central DAO manager that just picked up the main DAO class references for the individual modules somewhere.  This would allow easy installation of new modules by outside developers (which is key).  It would also make our life easier.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.jlcp.org/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira