directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Conlon (JIRA)" <>
Subject [jira] Updated: (DIRSERVER-659) Upgrade OSGi Configuration Admin
Date Sat, 01 Jul 2006 18:48:30 GMT
     [ ]

John Conlon updated DIRSERVER-659:

    Attachment: configuration-src_main_java.patch

Patched src/main/java directory. 

While this code is  providing the bulk of Configuration Admin service functionality it is
still deficient in many respects. I consider this code sandbox quality and ready for review,
comments and discussion.   Will await further directions and comments.

There are a couple of new classes added to the directory, some fixes and some refactoring
of the old classes. There are also a couple of new features related to attributes:

1. Mapping LDAP attributes to OSGi attributes requires a mapping because many of the attributes
of standard OSGi services require periods in their names.  Previously mapping was done in
the main code.  Now Attribute name mapping is done by a new class called AttributeMappingConfigurationPlugin
which implements ConfigurationPlugin.  AttributeMappingConfigurationPlugin is a simple POJO
declared as a component by the metadata.xml and thus started by the servicebinder.

2.  Simple attribute types can be encapsulated in arrays or Vectors as specified by the configurationAdmin
spec and thus multivalue LDAP attributes in the backing store can be used for configuraition
Admin.  In this initial version vectors are used to encapsulate multivalue attributes.  

> Upgrade OSGi Configuration Admin
> --------------------------------
>          Key: DIRSERVER-659
>          URL:
>      Project: Directory ApacheDS
>         Type: Improvement

>     Reporter: John Conlon
>  Attachments: configuration-pom.xml.patch, configuration-src_main_java.patch, configuration-src_test_java.patch,
> Upgrade the OSGi Configuration Admin Service for M2 and OSGi R4

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message