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] Resolved: (DIRSTUDIO-667) I want to specify the type and cardinality of members of the generated Java bean class
Date Wed, 28 Jul 2010 16:27:16 GMT

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

Kasun Lakpriya resolved DIRSTUDIO-667.
--------------------------------------

    Resolution: Fixed

Resolved : http://code.google.com/p/dirstudio-ldap-tooling/source/detail?r=94

> I want to specify the type and cardinality of members of the generated Java bean class
> --------------------------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-667
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-667
>             Project: Directory Studio
>          Issue Type: Improvement
>          Components: studio-persistence-tooling
>            Reporter: Stefan Seelmann
>
> The current implementation automatically uses "Object" as type for all members of the
generated Java bean class. 
> It would be nice to be able to specify the Java type and the cardiality.
> The table viewer of DIRSTUDIO-666 should be extended by two columns.
> In the 1st new column the user can specify the Java type. The cell viewer should be a
drop-down box with the following posssible values
> - String
> - int
> - long
> - boolean
> - byte[]
> - Calendar
> The default value depends on the LDAP syntax and the attribute type:
> - 1.3.6.1.4.1.1466.115.121.1.49 (Integer): int
> - 1.3.6.1.4.1.1466.115.121.1.7 (Boolean): boolean
> - 1.3.6.1.4.1.1466.115.121.1.24 (Generalized Time): Calendar
> - if attribute type is binary (see SchemaUtils.isBinary()): byte[]
> - otherwise: String
> in the 2nd new column the user can define the cardinality:
> - 0..1
> - 1
> - 0..N
> - 1..N
> The default values depend on the object class, attribute type and syntax:
> - if the attribute is defined as "must" in the object class the lower bound is 1, otherwise
it is 0 
> - if the LDAP attribute type is single-valued the upper bound is 1, otherwise it is N
> For multi-valued attributes the user should also be able to specify if he wants to use
a Set (default), a List, or an Array.

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