You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by di...@incubator.apache.org on 2004/07/10 05:17:08 UTC

[jira] Created: (DIREVE-16) Move backend in sandbox into trunk, consolidate, & integrate

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIREVE-16

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIREVE-16
    Summary: Move backend in sandbox into trunk, consolidate, & integrate
       Type: Task

     Status: Unassigned
   Priority: Major

    Project: Directory Eve
 Components: 
             Backend

   Assignee: 
   Reporter: Alex Karasulu

    Created: Fri, 9 Jul 2004 8:16 PM
    Updated: Fri, 9 Jul 2004 8:16 PM

Description:
Currently the sandbox contains a new backend design with two new backend partitions: the system backend partition and the default backend partition. 

The system backend partition is a special case of the default backend partition.  This special backend partition supports aliases using a new algorithm for alias dereferrencing so its pretty slick.  This stuff is written directly to be Merlin components.

We need to move this stuff into the trunk and consolidate things into an API, IMPL and merlin project instead of having each component be its own project.  We're going to have to do this consolidation but at the same time we need to POJO-ify the components within.  That means creating monitors where there were none, creating Configuration beans and other things to be able to have pojo implementations of the components.

This task could be broken down into many smaller tasks.



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

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

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


[jira] Closed: (DIREVE-16) Move backend in sandbox into trunk, consolidate, & integrate

Posted by di...@incubator.apache.org.
Message:

   The following issue has been closed.

   Resolver: Alex Karasulu
       Date: Sat, 23 Oct 2004 1:31 AM

All done! Don't need that sandbox anymore.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIREVE-16

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIREVE-16
    Summary: Move backend in sandbox into trunk, consolidate, & integrate
       Type: Task

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Directory Eve
 Components: 
             jndi-provider

   Assignee: 
   Reporter: Alex Karasulu

    Created: Fri, 9 Jul 2004 8:16 PM
    Updated: Sat, 23 Oct 2004 1:31 AM

Description:
Currently the sandbox contains a new backend design with two new backend partitions: the system backend partition and the default backend partition. 

The system backend partition is a special case of the default backend partition.  This special backend partition supports aliases using a new algorithm for alias dereferrencing so its pretty slick.  This stuff is written directly to be Merlin components.

We need to move this stuff into the trunk and consolidate things into an API, IMPL and merlin project instead of having each component be its own project.  We're going to have to do this consolidation but at the same time we need to POJO-ify the components within.  That means creating monitors where there were none, creating Configuration beans and other things to be able to have pojo implementations of the components.

This task could be broken down into many smaller tasks.



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

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

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