directory-api mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lécharny <>
Subject Re: Upgrade Issues / Dealing with OSGI
Date Fri, 24 Apr 2015 21:39:12 GMT
Le 24/04/15 21:05, Gregory Chanan a écrit :
> Stefan: How do I tell if I'm in an OSGi environment or not?  I don't know
> much about OSGi and I don't think I am using it (at least, I haven't done
> anything specific in the application to turn on OGSi).  I just thought OSGI
> might be the issue because it looked like a classloader issue and I saw
> osgi in the package name.  Is there any harm in using the
> DefaultLdapCodecService over the StandaloneLdapApiService even if I'm not
> in an OSGi environment?  What's the difference?

Not surre what the pb can be, but with the getters/setters, its hsould
be saved
> Emmanuel: thanks for the fix, I'm still trying to test it; running into
> some mvn versioning issues.  Is there a guide for what version of directory
> server I need to use with which version of the ldap api?  I'm using M15
> directory server versions and M30-SNAPSHOT ldap apis.  With this, I get
> NoSuchMethodError on the functions you added (because the
> api-ldap-codec-core gets pulled in as M20 from a server dependency); if I
> change the order of the dependencies I get java.lang.NoClassDefFoundError:
> org/apache/directory/api/ldap/schemaloader/SchemaEntityFactory.

Due to the various changes made in both projects, you have to use

We are working on releasing those two guys this week-end.

View raw message