directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thom Park" <>
Subject RE: Problem embedding 0.92 ApacheDS...
Date Fri, 30 Sep 2005 14:53:22 GMT
Hi Nick,


Sorry - I apologize for not getting feedback to you - I got a bit lost
in the weeds with the problems we were having with schema parsing.


 Unfortunately,  we still have the same issue of  an incompatability
between log4J and slf4j.

We rolled our release back to ApacheDS 0.9 for now, such that we were
able to progress further but obviously, we'll need to solve this problem
to continue using the newer versions of ApacheDS.






From: Nick Faiz [] 
Sent: Thursday, September 29, 2005 9:43 PM
To: Apache Directory Developers List
Subject: Re: Problem embedding 0.92 ApacheDS...



Can you let me know if recompiling fixed the logger incompatibility? If
it did we can document it somewhere. If it didn't we'll have to find
another fix.


On 9/30/05, Nick Faiz <> wrote:



We're sorry that you're seeing this problem.


Are you able to recompile 0.9.2 from source and include that result in
your app.? If so, could you open apacheds/trunk/project.xml and replace
the current nlog4j dependency with this:










Running `maven -Dmaven.test.skip=true multiproject:install ` at the same
location will compile the jars for you.


I can't guarantee that this will fix the problem but I think the 0.9.2
version uses nlog4j 1.2.14, which was having issues along these lines.





On 30/09/2005, at 5:13 AM, Thom Park wrote: 



After following the steps in ServerMain, I'm now getting loads of errors
from log4J: 


If I have the ApacheDS down the classpath from my application, I find I
get this error:


SLF4J built for org.slf4j.impl.Log4jLoggerFA

Exception in thread "main" java.lang.IncompatibleClassChangeError 

at org.apache.ldap.server.jndi.ServerContextFactory.startLdapProtocol( )

at org.apache.ldap.server.jndi.ServerContextFactory.afterStartup( :108 )

at org.apache.ldap.server.jndi.DefaultContextFactoryService.startup( )

at org.apache.ldap.server.jndi.AbstractContextFactory.getInitialContext( :99 )

at javax.naming.spi.NamingManager.getInitialContext( )

at javax.naming.InitialContext.getDefaultInitCtx( )

at javax.naming.InitialContext.init ( )

at javax.naming.InitialContext.<init>( )

at<init>( )

at com.borland.sdop.registry.server.RegistryServer.initialDirContext ( )

at com.borland.sdop.registry.server.RegistryServer.setupRegistryEngine( )

at )

at com.borland.sdop.registry.server.RegistryProcess.main ( )


This is being emitted from the ApacehDS classes, prior to loading them
all log4J messages were emitted correctly to the log.

Now, I understand you're picking up our log4J in the classpath - but -
if I then move the ApacheDS jars ahead of mine in the classpath I get:


Exception in thread "main" java.lang.NoSuchMethodError:

at blah.blah.RegistryProcess.installShutdownHandler( )

at blah.blah.RegistryProcess.main( )

it appears to me that the method "debug" that handles an array of
objects is missing from the logger implementation bundled with ApacheDS.


Is there anywhere in the ApacheDS documentation that describes how to
configure ApacheDS to co-exist with 'normal' log4J - to change our
application over to a non-standard log4J would be a non-trivial
undertaking at this point.











From: Trustin Lee [] 
Sent: Wednesday, September 28, 2005 5:32 PM
To: Apache Directory Developers List 
Subject: Re: Problem embedding 0.92 ApacheDS...


Hi Thom,

2005/9/29, Thom Park <
<> >:

I've followed the instructions in the doc for embedding ApacheDS in my
java application but, what worked fine with 0.9 no longer works with

Can someone tell me what's changed with the procedure to embed ApacheDS
0.92 within a java app and put me right please?

The way to configure ApacheDS has been change significantly from 0.9.2.
There's no documentation about it, but please take a look at
apacheds-main to find out how to configure ApacheDS.   It is using
Spring framework, but you can configure it plain Java code, too. 

what we call human nature is actually human habit 



View raw message