|
Home > Archive > Apache Directory Project > October 2005 > Problem embedding 0.92 ApacheDS...
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Problem embedding 0.92 ApacheDS...
|
|
| Thom Park 2005-09-28, 5:45 pm |
| Hi,
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 =
0.92!
Can someone tell me what's changed with the procedure to embed ApacheDS =
0.92 within a Java app and put me right please?
-Thom
-----Original Message-----
From: Emir Rodriguez [mailto:emirrodriguex2-/E1597aS9LQGXtTpemXPTA@public.gmane.org]=20
Sent: Monday, September 26, 2005 3:35 PM
To: dev-aYN4UCa7k1r1N9kud6OZbmD2FQJk+8+b@public.gmane.org
Subject: [mina] Problems with the SSLFilter=20
Hello,
I'm new using the SSL with Mina, I'm trying to make a
simple program that can connect to the Echo server
that comes with the project, but it never can write
the message over the network.
- I enable the flag in the Main class of the Echo
Server example.
- I'm using the 0.9 SNAPSHOT version of MINA.
- And this is the simple code that i'm using to
connect to the server.
public static void main(String[] args) throws
Exception {
// Create TCP/IP connector.
SocketConnector connector =3D new SocketConnector();
try {
=20
connector.getFilterChain().addLast("sslFilterClient",
new
SSLFilter(BogusSSLContextFactory.getInstance(false)));
ConnectFuture future =3D connector.connect(new
InetSocketAddress("10.0.50.199", 8080), new
NetCatProtocolHandler());
future.join();
if (!future.isConnected())
System.out.println("No se conecto");
} catch (IOException e) {
e.printStackTrace();
} catch (Exception e) {
e.printStackTrace();
}
}
I dont know what happend ? i'm making some wrong. !!!
P
=09
=09
=09
________________________________________
___________________=20
Do You Yahoo!?=20
La mejor conexi=F3n a Internet y <b >2GB</b> extra a tu correo por $100 =
al mes. http://net.yahoo.com.mx=20
| |
| Trustin Lee 2005-09-28, 8:45 pm |
| Hi Thom,
2005/9/29, Thom Park <Thom.Park-uJD6bB5IadxBDgjK7y7TUQ@public.gmane.org>:
>
> 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 0.92!
>
> 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.
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
| |
| Thom Park 2005-09-29, 5:45 pm |
| Hmm...
Well, I guess I have to read the code some time - now is as good as any.
Thanks,
-Thom
________________________________
From: Trustin Lee [mailto:trustin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
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 <Thom.Park-uJD6bB5IadxBDgjK7y7TUQ@public.gmane.org>:
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
0.92!
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.
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
| |
| Thom Park 2005-09-29, 5:45 pm |
| Hmm...
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(Serve
rContextFactory.java:222)
at
org.apache.ldap.server.jndi.ServerContextFactory.afterStartup(ServerCont
extFactory.java:108)
at
org.apache.ldap.server.jndi.DefaultContextFactoryService.startup(Default
ContextFactoryService.java:204)
at
org.apache.ldap.server.jndi.AbstractContextFactory.getInitialContext(Abs
tractContextFactory.java:99)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at
javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:8
2)
at
com.borland.sdop.registry.server.RegistryServer.initialDirContext(Regist
ryServer.java:158)
at
com.borland.sdop.registry.server.RegistryServer.setupRegistryEngine(Regi
stryServer.java:169)
at
com.borland.sdop.registry.server.RegistryServer.run(RegistryServer.java:
51)
at
com.borland.sdop.registry.server.RegistryProcess.main(RegistryProcess.ja
va:50)
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:
org.apache.log4j.Logger.debug(Ljava/lang/Object;)V
at
blah.blah.RegistryProcess.installShutdownHandler(RegistryProcess.java:14
6)
at blah.blah.RegistryProcess.main(RegistryProcess.java:39)
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.
-Thom
________________________________
From: Trustin Lee [mailto:trustin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
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 <Thom.Park-uJD6bB5IadxBDgjK7y7TUQ@public.gmane.org>:
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
0.92!
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.
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
| |
| Nick Faiz 2005-09-29, 5:45 pm |
| Thom,
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:
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>nlog4j</artifactId>
<version>1.2.17</version>
<url>http://slf4j.org/nlog4j</url>
</dependency>
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.
Cheers,
Nick
On 30/09/2005, at 5:13 AM, Thom Park wrote:
> Hmm…
>
>
>
> 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
> (ServerContextFactory.java:222)
>
> at org.apache.ldap.server.jndi.ServerContextFactory.afterStartup
> (ServerContextFactory.java:108)
>
> at org.apache.ldap.server.jndi.DefaultContextFactoryService.startup
> (DefaultContextFactoryService.java:204)
>
> at
> org.apache.ldap.server.jndi.AbstractContextFactory.getInitialContext
> (AbstractContextFactory.java:99)
>
> at javax.naming.spi.NamingManager.getInitialContext
> (NamingManager.java:667)
>
> at javax.naming.InitialContext.getDefaultInitCtx
> (InitialContext.java:247)
>
> at javax.naming.InitialContext.init(InitialContext.java:223)
>
> at javax.naming.InitialContext.<init>(InitialContext.java:197)
>
> at javax.naming.directory.InitialDirContext.<init>
> (InitialDirContext.java:82)
>
> at com.borland.sdop.registry.server.RegistryServer.initialDirContext
> (RegistryServer.java:158)
>
> at
> com.borland.sdop.registry.server.RegistryServer.setupRegistryEngine
> (RegistryServer.java:169)
>
> at com.borland.sdop.registry.server.RegistryServer.run
> (RegistryServer.java:51)
>
> at com.borland.sdop.registry.server.RegistryProcess.main
> (RegistryProcess.java:50)
>
>
>
> 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:
> org.apache.log4j.Logger.debug(Ljava/lang/Object;)V
>
> at blah.blah.RegistryProcess.installShutdownHandler
> (RegistryProcess.java:146)
>
> at blah.blah.RegistryProcess.main(RegistryProcess.java:39)
>
> 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.
>
>
>
> -Thom
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Trustin Lee [mailto:trustin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
> 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 <Thom.Park-uJD6bB5IadxBDgjK7y7TUQ@public.gmane.org>:
>
> 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 0.92!
>
> 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.
>
> Trustin
> --
> what we call human nature is actually human habit
> --
> http://gleamynode.net/
>
>
| |
| Nick Faiz 2005-09-30, 2:45 am |
| Thom,
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.
Cheers,
Nick
On 9/30/05, Nick Faiz <nickfaiz@gmail.com> wrote:
>
> Thom,
> 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:
>
>
> <dependency>
> <groupId>org.slf4j</groupId>
> <artifactId>nlog4j</artifactId>
> <version>1.2.17</version>
> <url>http://slf4j.org/nlog4j</url>
> </dependency>
>
> 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.2version uses nlog4j
> 1.2.14, which was having issues along these lines.
>
> Cheers,
> Nick
>
> On 30/09/2005, at 5:13 AM, Thom Park wrote:
>
> Hmm…
>
> 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(*
> ServerContextFactory.java:222*)
>
> at org.apache.ldap.server.jndi.ServerContextFactory.afterStartup(*
> ServerContextFactory.java:108*)
>
> at org.apache.ldap.server.jndi.DefaultContextFactoryService.startup(*
> DefaultContextFactoryService.java:204*)
>
> at org.apache.ldap.server.jndi.AbstractContextFactory.getInitialContext(*
> AbstractContextFactory.java:99*)
>
> at javax.naming.spi.NamingManager.getInitialContext(*NamingManager.java
> :667*)
>
> at javax.naming.InitialContext.getDefaultInitCtx(*InitialContext.java:247*
> )
>
> at javax.naming.InitialContext.init(*InitialContext.java:223*)
>
> at javax.naming.InitialContext.<init>(*InitialContext.java:197*)
>
> at javax.naming.directory.InitialDirContext.<init>(*InitialDirContext.java
> :82*)
>
> at com.borland.sdop.registry.server.RegistryServer.initialDirContext(*
> RegistryServer.java:158*)
>
> at com.borland.sdop.registry.server.RegistryServer.setupRegistryEngine(*
> RegistryServer.java:169*)
>
> at com.borland.sdop.registry.server.RegistryServer.run(*
> RegistryServer.java:51*)
>
> at com.borland.sdop.registry.server.RegistryProcess.main(*
> RegistryProcess.java:50*)
>
> 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:
> org.apache.log4j.Logger.debug(Ljava/lang/Object;)V
>
> at blah.blah.RegistryProcess.installShutdownHandler(*RegistryProcess.java
> :146*)
>
> at blah.blah.RegistryProcess.main(*RegistryProcess.java:39*)
>
> 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.
>
> -Thom
>
> ------------------------------
>
> *From:* Trustin Lee [mailto:trustin@gmail.com <trustin@gmail.com>]
> *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 <Thom.Park@borland.com>:
>
> 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 0.92!
>
> 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.
>
> Trustin
> --
> what we call human nature is actually human habit
> --
> http://gleamynode.net/
>
>
>
| |
| Thom Park 2005-09-30, 5:45 pm |
| 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.
-Thom
________________________________
From: Nick Faiz [mailto:nickfaiz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
Sent: Thursday, September 29, 2005 9:43 PM
To: Apache Directory Developers List
Subject: Re: Problem embedding 0.92 ApacheDS...
Thom,
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.
Cheers,
Nick
On 9/30/05, Nick Faiz <nickfaiz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
Thom,
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:
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>nlog4j</artifactId>
<version>1.2.17</version>
<url>http://slf4j.org/nlog4j</url>
</dependency>
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.
Cheers,
Nick
On 30/09/2005, at 5:13 AM, Thom Park wrote:
Hmm...
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(
ServerContextFactory.java:222 )
at org.apache.ldap.server.jndi.ServerContextFactory.afterStartup(
ServerContextFactory.java :108 )
at org.apache.ldap.server.jndi.DefaultContextFactoryService.startup(
DefaultContextFactoryService.java:204 )
at org.apache.ldap.server.jndi.AbstractContextFactory.getInitialContext(
AbstractContextFactory.java :99 )
at javax.naming.spi.NamingManager.getInitialContext(
NamingManager.java:667 )
at javax.naming.InitialContext.getDefaultInitCtx(
InitialContext.java:247 )
at javax.naming.InitialContext.init ( InitialContext.java:223 )
at javax.naming.InitialContext.<init>( InitialContext.java:197 )
at javax.naming.directory.InitialDirContext.<init>(
InitialDirContext.java:82 )
at com.borland.sdop.registry.server.RegistryServer.initialDirContext (
RegistryServer.java:158 )
at com.borland.sdop.registry.server.RegistryServer.setupRegistryEngine(
RegistryServer.java:169 )
at com.borland.sdop.registry.server.RegistryServer.run(
RegistryServer.java:51 )
at com.borland.sdop.registry.server.RegistryProcess.main (
RegistryProcess.java:50 )
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:
org.apache.log4j.Logger.debug(Ljava/lang/Object;)V
at blah.blah.RegistryProcess.installShutdownHandler(
RegistryProcess.java:146 )
at blah.blah.RegistryProcess.main( RegistryProcess.java:39 )
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.
-Thom
________________________________
From: Trustin Lee [mailto:trustin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
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 < Thom.Park-uJD6bB5IadxBDgjK7y7TUQ@public.gmane.org
<mailto:Thom.Park-uJD6bB5IadxBDgjK7y7TUQ@public.gmane.org> >:
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
0.92!
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.
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
| |
| Ceki Gülcü 2005-10-11, 7:45 am |
|
Hello Thom,
Here is a quick question for you. Does your set up use log4j version 1.2.x=
=20
or 1.3.x?
Thank you in advance for your response,
At 09:13 PM 9/29/2005, Thom Park wrote:
>Hmm=85
>
>After following the steps in ServerMain, I=92m now getting loads of errors=
=20
>from log4J:
>
>If I have the ApacheDS down the classpath from my application, I find I=20
>get this error:
>
>
>SLF4J built for org.slf4j.impl.Log4jLoggerFA
>
>Exception in thread "main" java.lang.IncompatibleClassChangeError
>
>at=20
>org.apache.ldap.server.jndi.ServerContextFactory.startLdapProtocol(ServerCo=
ntextFactory.java:222)
>
>at=20
>org.apache.ldap.server.jndi.ServerContextFactory.afterStartup(ServerContext=
Factory.java:108)
>
>at=20
>org.apache.ldap.server.jndi.DefaultContextFactoryService.startup(DefaultCon=
textFactoryService.java:204)
>
>at=20
>org.apache.ldap.server.jndi.AbstractContextFactory.getInitialContext(Abstra=
ctContextFactory.java:99)
>
>at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
>
>at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
>
>at javax.naming.InitialContext.init(InitialContext.java:223)
>
>at javax.naming.InitialContext.<init>(InitialContext.java:197)
>
>at=
javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:82)
>
>at=20
>com.borland.sdop.registry.server.RegistryServer.initialDirContext(RegistryS=
erver.java:158)
>
>at=20
>com.borland.sdop.registry.server.RegistryServer.setupRegistryEngine(Registr=
yServer.java:169)
>
>at=
com.borland.sdop.registry.server.RegistryServer.run(RegistryServer.java:51)
>
>at=20
>com.borland.sdop.registry.server.RegistryProcess.main(RegistryProcess.java:=
50)
>
>This is being emitted from the ApacehDS classes, prior to loading them all=
=20
>log4J messages were emitted correctly to the log.
>Now, I understand you=92re picking up our log4J in the classpath =96 but =
=96 if=20
>I then move the ApacheDS jars ahead of mine in the classpath I get:
>
>
>Exception in thread "main" java.lang.NoSuchMethodError:=20
>org.apache.log4j.Logger.debug(Ljava/lang/Object;)V
>
>at=
blah.blah.RegistryProcess.installShutdownHandler(RegistryProcess.java:146)
>
>at blah.blah.RegistryProcess.main(RegistryProcess.java:39)
>it appears to me that the method =93debug=94 that handles an array of=
objects=20
>is missing from the logger implementation bundled with ApacheDS.
>
>Is there anywhere in the ApacheDS documentation that describes how to=20
>configure ApacheDS to co-exist with =91normal=92 log4J =96 to change our=20
>application over to a non-standard log4J would be a non-trivial=20
>undertaking at this point.
>
>-Thom
>
>
>
>
>
>
>
>
>
>
>----------
>From: Trustin Lee [mailto:trustin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
>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 <<mailto:Thom.Park-uJD6bB5IadxBDgjK7y7TUQ@public.gmane.org>Thom.Park-uJD6bB5IadxBDgjK7y7TUQ@public.gmane.org>:
>I've followed the instructions in the doc for embedding ApacheDS in my=20
>java application but, what worked fine with 0.9 no longer works with 0.92!
>
>Can someone tell me what's changed with the procedure to embed ApacheDS=20
>0.92 within a Java app and put me right please?
>
>The way to configure ApacheDS has been change significantly from=20
>0.9.2. There's no documentation about it, but please take a look at=20
>apacheds-main to find out how to configure ApacheDS. It is using Spring=
=20
>framework, but you can configure it plain Java code, too.
>
>Trustin
>--
>what we call human nature is actually human habit
>--
><http://gleamynode.net/>http://gleamynode.net/
--=20
Ceki G=FClc=FC
The complete log4j manual: http://www.qos.ch/log4j/
|
|
|
|
|