directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Athoya Hettige Kasun Lakpriya (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSTUDIO-664) Create a first prototype to generate a java bean class from an LDAP entry
Date Fri, 25 Jun 2010 19:47:50 GMT

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882690#action_12882690
] 

Athoya Hettige Kasun Lakpriya commented on DIRSTUDIO-664:
---------------------------------------------------------

Had some issues with selecting a code generator but after discussed with Stefan Seelmann was
able to select the Apache Velocity as the template engine.
The issue of extracting the "Most specific structural object class" of a selected entry was
resolved by adding another SchemaUtils class to the persistence-core module of the persistence-tooling.

After having some IRC discussions changed the algorithm in SchemaUtils class and now working
fine.

> Create a first prototype to generate a java bean class from an LDAP entry
> -------------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-664
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-664
>             Project: Directory Studio
>          Issue Type: Improvement
>          Components: studio-persistence-tooling
>            Reporter: Stefan Seelmann
>            Assignee: Athoya Hettige Kasun Lakpriya
>
> From the directory-dev mailing list:
> I think it's time to make your hands dirty :-). You already mentioned in IRC that you'd
like to start with path A, that's great. I'd recommend to create a first prototype:
> - Create an new UI plugin that adds a new menu item to the LDAP Browser context menu
used to select an entry and to call the analyzer
> - Create a simple version of "LDAP entry and schema Analyzer" that just extracts the
structural object class from the entry and all user attributes from the schema
> - Select a template engine for the code generator
> - Create a simple template that just generates a Java class named like the structural
object class (capitalize the first letter) and with attributes (type Object) for all user
attributes. No DAO yet.
> So for example, when selecting an inetOrgPerson" entry the generated Java class looks
like this:
> public InetOrgPerson
> {
>    private Object objectClass
>    private Object cn;
>    private Object givenName;
>    private Object telephoneNumber;
>    ....
> }

-- 
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