directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kasun Lakpriya (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DIRSTUDIO-644) Object LDAP Persistence Tooling
Date Sat, 28 Aug 2010 18:54:53 GMT

     [ https://issues.apache.org/jira/browse/DIRSTUDIO-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kasun Lakpriya updated DIRSTUDIO-644:
-------------------------------------

    Attachment: persistence-tooling.tar.gz

- Here I have attached the work I have done during my GSoC program(2010) with my mentor Stefan
Seelmann and Apache Directory Community.

- To continue working on this in Directory I have signed an ICLA and got the confirmation
saying "ICLA has been filed".

- Current tooling still only supports the (1st) scenario mentioned above. 

> Object LDAP Persistence Tooling
> -------------------------------
>
>                 Key: DIRSTUDIO-644
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-644
>             Project: Directory Studio
>          Issue Type: New Feature
>          Components: studio-persistence-tooling
>            Reporter: Stefan Seelmann
>            Assignee: Stefan Seelmann
>         Attachments: persistence-tooling.tar.gz
>
>
> It would be nice to add Object to LDAP persistence tooling to Apache Directory Studio.
>  
> The tooling should support two scenarios:
> 1st) Based on an existing directory tree and schema the domain model and persistence
code (DAOs) should be generated. The idea is to select an example entry in the LDAP Browser,
right-click, and generate the code into an Eclipse Java project.
> 2nd) Based on an existing domain model (e.g. Java classes) an LDAP schema and persistence
code (DAOs) should be generated. The idea is to select a package in the Eclipse Package Explorer,
right-click, and generate the code.
>  
> A special challenge will be the support of object relationships, e.g. Departments-Users-Groups-Roles-Permissions.
In LDAP such relationships are often implemented using hierarchies, DN references, or attribute
references.
>  
> The main focus should be the generation of Java code. However it would be nice if the
code generators would be pluggable to make it possible to create code for different languages
(Scala, C#, etc.). It would also be nice to support different persistence engines, for example
plain JNDI, the Apache LDAP API, or DataNucleus.
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message