[
https://issues.apache.org/jira/browse/DIRSTUDIO-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882642#action_12882642
]
Athoya Hettige Kasun Lakpriya commented on DIRSTUDIO-664:
---------------------------------------------------------
Architecture diagram previously added can be found at
http://code.google.com/p/dirstudio-ldap-tooling/wiki/ArchitectureDiagram.
> 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.
