From dev-return-34374-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Fri Jun 25 19:48:12 2010 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 67443 invoked from network); 25 Jun 2010 19:48:12 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 25 Jun 2010 19:48:12 -0000 Received: (qmail 66838 invoked by uid 500); 25 Jun 2010 19:48:12 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 66740 invoked by uid 500); 25 Jun 2010 19:48:11 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 66730 invoked by uid 99); 25 Jun 2010 19:48:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jun 2010 19:48:11 +0000 X-ASF-Spam-Status: No, hits=-1545.7 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jun 2010 19:48:10 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o5PJloXX022110 for ; Fri, 25 Jun 2010 19:47:50 GMT Message-ID: <22008348.64741277495270128.JavaMail.jira@thor> Date: Fri, 25 Jun 2010 15:47:50 -0400 (EDT) From: "Athoya Hettige Kasun Lakpriya (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIRSTUDIO-664) Create a first prototype to generate a java bean class from an LDAP entry In-Reply-To: <19758512.58021277470610287.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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.