directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Created: (DIRSTUDIO-305) Add hooks for OLM operations
Date Thu, 20 Mar 2008 15:23:24 GMT
Add hooks for OLM operations

                 Key: DIRSTUDIO-305
             Project: Directory Studio
          Issue Type: New Feature
            Reporter: Alex Karasulu

We're kicking off or trying to at least a new project to create an Object-LDAP Mapping tool.
 This tool will most likely have some core libraries to bidirectionally generate schema from
POJOs and vice versa.  These core libs will be used by a maven plugin to enable users to stay
focused on the use of domain objects instead of being bogged down with the overhead of mundane
persistence operations.  FYI such a library also provides annotations and can optionally use
schema extension information to override default mapping strategies.

It would be nice if studio can hook into this API to allow users to generate code or schema
from server connections or existing domain object classes respectively.  There might need
to be some integration between the schema browser here but I don't know.

The primary aim here is to facilitate a couple of neat use cases for our users:

(1) User right clicks on a connection object or a set of schema entities in the schema browser
and uses a context menu to generate POJO classes and their persistence managers.  Users then
use these domain objects in their LDAP enabled applications instead of manually managing persistence

(2) User right clicks on a Java package in the package explorer of eclipse, and uses a context
popup menu to select a generate schema menu item.  This may launch some kind of wizard to
gather schema generation heuristics or overrides to the the default mapping strategy.  Incidentally
even for use case #1 above we might have such a wizard going in the opposite direction.  So
this would generate a schema which can be viewed by the user and edited, ultimately to be
saved either to a file or deployed to a specific connection in studio.

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

View raw message