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

[email protected] Thu, 2 Oct 2003 09:08:26 -0500 (CDT)
Newsgroups gmane.comp.java.javalobby.communityplatform
Message-ID <[email protected]>
Message:

   The following issue has been closed.

   Resolver: Matthew Schmidt
       Date: Thu, 2 Oct 2003 9:07 AM

We're not using this anymore, it will essentially go away with the new persistence layer.
---------------------------------------------------------------------
View the issue:

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


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

     Status: Closed
   Priority: Critical
 Resolution: WON'T FIX

 Original Estimate: 0 minutes
 Time Spent: Unknown
  Remaining: 0 minutes

    Project: Javalobby Community Platform
   Fix Fors:
             0.9.0 (Jupiter)
   Versions:
             0.5.0 (Delorean)

   Assignee: J Aaron Farr
   Reporter: Matthew Schmidt

    Created: Wed, 9 Apr 2003 8:03 AM
    Updated: Thu, 2 Oct 2003 9:07 AM

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.javalobby.org/secure/Administrators.jspa

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