directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Karasulu <>
Subject Re: [ApacheDS 2.0] OSGI, Implementing Services
Date Thu, 20 Oct 2011 11:06:06 GMT
On Wed, Oct 19, 2011 at 10:20 AM, Emmanuel Lecharny <>wrote:

> On 10/19/11 9:08 AM, Pierre-Arnaud Marcelot wrote:
>> Hi Göktürk,
>> On 19 oct. 2011, at 06:35, Göktürk Gezer wrote:
>>  Hi Emmanuel,
>>> I'm doing some experiments on DS. I saw some problems on our way. Before
>>> diving deeper i must consult you about somethings.
>>> I'm changing the way we deal with schema elements(LdapComparator,**Normalizer,SyntaxChecker)
>>> so that they will be pluggable. Schema manager tries to classload them
>>> that's where i'm going to change. I'll make SchemaManager get them through
>>> OSGI, but while i change the core parts, there are lots of place on the code
>>> that use them as tool(Tests espacially).
>> Although I'm 100% positive to move ApacheDS as a whole into OSGI, I'm
>> *really* not sure the LDAP API should rely on OSGI features for it's
>> extensibility.
>> As an API, it's meant to be used by many third party developers and I
>> personally think we can't afford to be only compatible with OSGI. I'm afraid
>> we still need to support the API as a set of simple jars (that's why we
>> added the 'standalone' project at the time with Alex, supporting both OSGI
>> and non-OSGI environments).
> To some extent, I feel a bit the same. It would be a real pain if we
> require that our users include an OSGi container in order to use our API.
> Now, is there a way to keep the schema elements class-loaded, without
> having to make them bundles ?
And this probably is the thought that triggered inquiries into using
fragments here.

Best Regards,
-- Alex

View raw message