<?xml version="1.0" encoding="ISO-8859-1" ?>
<configuration>
<jndi className="org.apache.commons.configuration.JNDIConfiguration" prefix="java:comp/env"/>
<dom4j className="org.apache.commons.configuration.DOM4JConfiguration" fileName="my-configuration.xml"/>
</configuration>
I invoke the factory like:
ConfigurationFactory factory = new ConfigurationFactory(); factory.setConfigurationFileName(configFile); Configuration config = factory.getConfiguration();
configFile here contains a fully qualified path to a file in WEB-INF.
My property reads look like:
String backColor = config.getString("my.property.name");
S
At 08:05 PM 4/3/2004 +0200, Eric Pugh wrote:
What classes in Configuration are you using? PropertiesConfiguration.java etc?
Eric
> -----Original Message----- > From: Steve Peterson [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 03, 2004 4:59 PM > To: Jakarta Commons Users List > Subject: Re: [configuration] configuration breaks tomcat autodeploy > > > To clarify my message, the only jar left after Tomcat undeploys my app is > the _configuration_ jar. > > At 08:50 AM 4/3/2004 -0600, you wrote: > > >I've just integrated the 0331 build of collections into my webapp and am > >running into a minor glitch. I deploy in Tomdat 5.0.18 with > >autodeploy. Prior to integrating collections I could do autodeploys by > >dropping a new war file into Tomcat's appBase. > > > >After integrating collections, and only if I invoke the collections api, > >autodeploy no longer works. Inspecting the deployment directory for my > >application, the only file left is the collections jar in > WEB-INF/lib, and > >java.exe that is running Tomcat looks like it still has the file > open. My > >hypothesis is that some file in the jar is being referenced and > not being > >closed. > > > >I tried expanding the jar into the WEB-INF/classes folder to > force the VM > >to read the file individually, but unfortunately the problem > doesn't occur > >in that deployment configuration. > > > >I'm out of ideas on how to run this down. I know I'll get complaints on > >Monday from the other developers on the project about autodeploy > breaking, > >so any help would be appreciated. > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
