You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "John Conlon (JIRA)" <ji...@apache.org> on 2006/12/15 01:56:21 UTC
[jira] Created: (DIRSERVER-798) Configurable ApacheDS OSGi bundles
require schema oid assignments
Configurable ApacheDS OSGi bundles require schema oid assignments
------------------------------------------------------------------
Key: DIRSERVER-798
URL: http://issues.apache.org/jira/browse/DIRSERVER-798
Project: Directory ApacheDS
Issue Type: New Feature
Affects Versions: 1.5.0
Reporter: John Conlon
Priority: Critical
An updated OSGi Config Admin Service implementation based on our JNDI backing store will soon be available for code review and experimental testing. This updated implementation of the OSGi Configuration Admin Service will use the jndi backing store to persist configuration admin data for it's clients based on custom schemas that are associated with each client type.
Several ApacheDS OSGi modules (like the protocol providers) will support dynamic configuration administration through the OSGi Configuration Admin service. Each of these OSGi Configuration Admin 'clients' will require a custom schema and thus an unique OID assignment.
To avoid OID collisions request that a branch of the the assigned ApacheDS OID tree be designated as the OSGi branch for OSGi schema OID assignments of required ApacheDS OSGi modules.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DIRSERVER-798) Configurable ApacheDS OSGi bundles
require schema oid assignments
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-798:
----------------------------------------
Fix Version/s: 2.5.0
OSGi is for 2.5
> Configurable ApacheDS OSGi bundles require schema oid assignments
> ------------------------------------------------------------------
>
> Key: DIRSERVER-798
> URL: https://issues.apache.org/jira/browse/DIRSERVER-798
> Project: Directory ApacheDS
> Issue Type: New Feature
> Reporter: John Conlon
> Assignee: Enrique Rodriguez
> Priority: Minor
> Fix For: 2.5.0
>
>
> An updated OSGi Config Admin Service implementation based on our JNDI backing store will soon be available for code review and experimental testing. This updated implementation of the OSGi Configuration Admin Service will use the jndi backing store to persist configuration admin data for it's clients based on custom schemas that are associated with each client type.
> Several ApacheDS OSGi modules (like the protocol providers) will support dynamic configuration administration through the OSGi Configuration Admin service. Each of these OSGi Configuration Admin 'clients' will require a custom schema and thus an unique OID assignment.
> To avoid OID collisions request that a branch of the the assigned ApacheDS OID tree be designated as the OSGi branch for OSGi schema OID assignments of required ApacheDS OSGi modules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRSERVER-798) Configurable ApacheDS OSGi
bundles require schema oid assignments
Posted by "Enrique Rodriguez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enrique Rodriguez reassigned DIRSERVER-798:
-------------------------------------------
Assignee: Enrique Rodriguez
> Configurable ApacheDS OSGi bundles require schema oid assignments
> ------------------------------------------------------------------
>
> Key: DIRSERVER-798
> URL: https://issues.apache.org/jira/browse/DIRSERVER-798
> Project: Directory ApacheDS
> Issue Type: New Feature
> Affects Versions: 1.5.0
> Reporter: John Conlon
> Assigned To: Enrique Rodriguez
> Priority: Critical
> Fix For: 1.5.2
>
>
> An updated OSGi Config Admin Service implementation based on our JNDI backing store will soon be available for code review and experimental testing. This updated implementation of the OSGi Configuration Admin Service will use the jndi backing store to persist configuration admin data for it's clients based on custom schemas that are associated with each client type.
> Several ApacheDS OSGi modules (like the protocol providers) will support dynamic configuration administration through the OSGi Configuration Admin service. Each of these OSGi Configuration Admin 'clients' will require a custom schema and thus an unique OID assignment.
> To avoid OID collisions request that a branch of the the assigned ApacheDS OID tree be designated as the OSGi branch for OSGi schema OID assignments of required ApacheDS OSGi modules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-798) Configurable ApacheDS OSGi bundles
require schema oid assignments
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-798:
----------------------------------------
OSGi should be integrated in 1.5.2, if everything is ready.
> Configurable ApacheDS OSGi bundles require schema oid assignments
> ------------------------------------------------------------------
>
> Key: DIRSERVER-798
> URL: https://issues.apache.org/jira/browse/DIRSERVER-798
> Project: Directory ApacheDS
> Issue Type: New Feature
> Affects Versions: 1.5.0
> Reporter: John Conlon
> Priority: Critical
> Fix For: 1.5.2
>
>
> An updated OSGi Config Admin Service implementation based on our JNDI backing store will soon be available for code review and experimental testing. This updated implementation of the OSGi Configuration Admin Service will use the jndi backing store to persist configuration admin data for it's clients based on custom schemas that are associated with each client type.
> Several ApacheDS OSGi modules (like the protocol providers) will support dynamic configuration administration through the OSGi Configuration Admin service. Each of these OSGi Configuration Admin 'clients' will require a custom schema and thus an unique OID assignment.
> To avoid OID collisions request that a branch of the the assigned ApacheDS OID tree be designated as the OSGi branch for OSGi schema OID assignments of required ApacheDS OSGi modules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-798) Configurable ApacheDS OSGi bundles
require schema oid assignments
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-798:
------------------------------------
Priority: Minor (was: Critical)
Affects Version/s: (was: 1.5.0)
Fix Version/s: (was: 1.5.2)
> Configurable ApacheDS OSGi bundles require schema oid assignments
> ------------------------------------------------------------------
>
> Key: DIRSERVER-798
> URL: https://issues.apache.org/jira/browse/DIRSERVER-798
> Project: Directory ApacheDS
> Issue Type: New Feature
> Reporter: John Conlon
> Assignee: Enrique Rodriguez
> Priority: Minor
>
> An updated OSGi Config Admin Service implementation based on our JNDI backing store will soon be available for code review and experimental testing. This updated implementation of the OSGi Configuration Admin Service will use the jndi backing store to persist configuration admin data for it's clients based on custom schemas that are associated with each client type.
> Several ApacheDS OSGi modules (like the protocol providers) will support dynamic configuration administration through the OSGi Configuration Admin service. Each of these OSGi Configuration Admin 'clients' will require a custom schema and thus an unique OID assignment.
> To avoid OID collisions request that a branch of the the assigned ApacheDS OID tree be designated as the OSGi branch for OSGi schema OID assignments of required ApacheDS OSGi modules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-798) Configurable ApacheDS OSGi bundles
require schema oid assignments
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-798:
----------------------------------------
Fix Version/s: 1.5.2
> Configurable ApacheDS OSGi bundles require schema oid assignments
> ------------------------------------------------------------------
>
> Key: DIRSERVER-798
> URL: https://issues.apache.org/jira/browse/DIRSERVER-798
> Project: Directory ApacheDS
> Issue Type: New Feature
> Affects Versions: 1.5.0
> Reporter: John Conlon
> Priority: Critical
> Fix For: 1.5.2
>
>
> An updated OSGi Config Admin Service implementation based on our JNDI backing store will soon be available for code review and experimental testing. This updated implementation of the OSGi Configuration Admin Service will use the jndi backing store to persist configuration admin data for it's clients based on custom schemas that are associated with each client type.
> Several ApacheDS OSGi modules (like the protocol providers) will support dynamic configuration administration through the OSGi Configuration Admin service. Each of these OSGi Configuration Admin 'clients' will require a custom schema and thus an unique OID assignment.
> To avoid OID collisions request that a branch of the the assigned ApacheDS OID tree be designated as the OSGi branch for OSGi schema OID assignments of required ApacheDS OSGi modules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.