directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Conlon (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-656) OSGi Configuration Admin requires AUXILIARY objectclasses
Date Tue, 27 Jun 2006 00:50:30 GMT
    [ ] 

John Conlon commented on DIRSERVER-656:

The OSGi Configuration Admin implementation will be required to support standard OSGi configuration
attributes.  Many of these attributes include a period in their name. (like, event.topics,
event.filter, etc).  If these standard attributes are not 'built in' to the ApacheDS OSGi
Admin (and specified as schemas) end users will be forced to not only create their own schemas
but implement their own implementations to support
mapping them from LDAP attributes.

 1. The existing OSGi objectclasses apacheServiceConfiguration, apacheFactoryConfiguration
and their attributes be defined in a schema file seperate from apache.schema. (named osgi.schema?)
 2. Top level oids be assigned for osgi objectclasses and attributes.  
 3. Assign standard tagging (auxiliary) objectclasses  for typical component functionality.
For example an eventhandler objectclass would be specified to model a component that implements
EventHandler. It would contain event.topics property and may contain an event.handler property.
 4. A base would be delivered as part of the Configuration
Admin service to map osgi specific ldap attributes to standard osgi attributes.

> OSGi Configuration Admin requires AUXILIARY objectclasses
> ---------------------------------------------------------
>          Key: DIRSERVER-656
>          URL:
>      Project: Directory ApacheDS
>         Type: Bug

>     Reporter: John Conlon
>  Attachments: apache.schema.patch
> The OSGi Configuration Admin service requires the two objectclasses, apacheServiceConfiguration
and apacheFactoryConfiguration specified in apache.schema be changed to tagging (AUXILIARY)

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