Hi Wayne, One bit of advice is to use the jcl104-over-slf4j package which is an implementation of commons-logging that maps to slf4j. Spring and many other projects use commons-logging, so this is a good way to make your logging setup consistent. So basically all you do is throw out commons-logging and add jcl104-overslf4j and you are all set. I have a blog entry about the commons-logging problems and how to use slf4j to fix it here: http://blog.organicelement.com/2006/12/21/commons-logging-classloader-woes/
Good luck, Chris On 7/17/07, Wayne Johnson <[EMAIL PROTECTED]> wrote:
I did finally figure it out. I was missing a slf4j jarfile. Part of my confusion was due to the myriad of loggers and logger wrappers involved. Our configuration is pretty complicated with Axis, Directory Service, Slide, an HTTP server and a few JSP web apps running under the Tanuki Java Service Wrapper. I apologize for not including more but I wasn't sure how to describe it without dropping 2 dozen configuration files on everyone. Thanks everyone for the suggestions. -----Original Message----- From: [EMAIL PROTECTED] on behalf of Alex Karasulu Sent: Tue 7/17/2007 4:15 PM To: [email protected] Subject: Re: Apache DS (I think) fails to load when we upgraded to Jetty 6.1.4 or 6.1.5rc0 How about providing more information on whether you have ADS embedded running in Jetty or in some app running both or ADS is standalone. Alex On 7/17/07, Wayne Johnson <[EMAIL PROTECTED]> wrote: > > I am trying to upgrade our Jetty & Apache DS (1.0.0) server From Jetty > 6.0.1 to Jetty 6.1.4 (or even Jetty 6.1.5rc0) and can't get Apache > Directory Service to load. Unfortunately, the only error I seem to get is: > > INFO | jvm 1 | 2007/07/17 12:50:04 | 2007-07-17 12:50:04.642::WARN: Config > error at <New id="factory" class=" > org.springframework.context.support.FileSystemXmlApplicationContext "><Arg>jetty/server.xml</Arg><Call > id="cfg" name="getBean"><Arg>configuration</Arg><Call id="jndi-env" > name="toJndiEnvironment"/></Call><Call id="env" > name="getBean"><Arg>environment</Arg><Call name="setProperty"><Arg><Get > name="INITIAL_CONTEXT_FACTORY" class="javax.naming.Context"/></Arg><Arg> > org.apache.directory.server.jndi.ServerContextFactory</Arg></Call><Call > name="putAll"><Arg><Ref id="jndi-env"/></Arg></Call></Call></New> > INFO | jvm 1 | 2007/07/17 12:50:04 | Configuration Exception: null > > I'm not sure if this is a problem in Jetty, or Apache DS, or our > configuration. Any ideas? Any hints on how to configure logging for a bit > more information? I tried adding a log4j.appender for directory service > but still nothing. > > I'll also post to the Jetty mailing list as well. Thanks. > > Wayne Johnson > Senior Software Engineer > MQSoftware, Inc. > 1660 S Highway 100 > Minneapolis, MN 55416 > (952) 345-8628 > > >
