This has been requested a couple times.. However no one has submitted a patch, and all the committers I think use it in an exploded format.. Patches welcome, it's all our code!
ERic > -----Original Message----- > From: Brian Lawler [mailto:[EMAIL PROTECTED] > Sent: Friday, February 06, 2004 8:23 PM > To: Turbine Users List > Subject: Re: Deploying WAR weith Turbine in it > > > Yeah, I recall trying this one before and being disappointed > that when > things got to the point of reading TR.props there was a filesystem > dependency rather than a getResourceAsStream. Perhaps a patch from > someone out there with copious spare time? > > -Brian > > > > On Friday, February 6, 2004, at 11:18 AM, Gerry Duprey wrote: > > > Howdy, > > > > I'm actually using Jetty which is a nice, small little Java server > > that can handle quite a load (and is very, very easy to > administer). > > If I explode the archive, then Turbine works, so I'm pretty sure I > > have things in the right place. > > > > It's too bad this doesn't work - there really isn't much of > a mystery > > to it. > > > > Gerry > > > > Mark Lybarger wrote: > >> Gerry, > >> What container are you using to deploy this to? There's something > >> about the way turbine tries to locate that file by using > >> getResourceAsStream or somesuch that it has problems running as a > >> .war. I guess there's some ambiguity in the spec on how the > >> containers implement that functionality and all. > >> We use wls 6.1, and our app has to be exploded (outside of > modifying > >> turbine code). Maybe a war works in 8.1, but i'm not quite sure. > >> Have you tried using an exploded web application? ~mark > >>> -----Original Message----- > >>> From: Gerry Duprey [mailto:[EMAIL PROTECTED] > >>> Sent: Friday, February 06, 2004 11:40 AM > >>> To: Turbine Users List > >>> Subject: Deploying WAR weith Turbine in it > >>> > >>> > >>> Howdy, > >>> > >>> I've gotten to the point that I'm trying to deploy a > turbine based > >>> app as a war file. > >>> > >>> The major stumbing block is that turbine cannot find it's > >>> TurbineResources.property file. The web.xml is exactly like the > >>> examples (using /WEB-INF/conf/TurbineResources.properties as the > >>> path and the file is definetly there). > >>> > >>> If I unpack the WAR file and point the appserver at the unpacked > >>> directory, Turbine can see the properties files (other > things break, > >>> but not turbines fault). > >>> > >>> Is anyone aware of anything special you have to do to > make Turbine > >>> be able to read it's config file when still in a .war file? The > >>> rest of my code has no problem finding files in the /WEB-INF > >>> directory, so I know it's doable (in the technical sense). > >>> > >>> Thanks for any pointers, > >>> > >>> Gerry > >>> -- > >>> Gerry Duprey > >>> ________________________________________ > >>> SchoolsOPEN, LLC > >>> 123 North Ashley, Suite 120 > >>> Ann Arbor, MI 48104 > >>> Phone (877) 483-1944 Ext. 401 > >>> Fax (734) 661-0819 > >>> > >>> Visit us Online at www.Schools-OPEN.com > >>> > >>> > >>> > --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: > [EMAIL PROTECTED] > >>> For additional commands, e-mail: > [EMAIL PROTECTED] > >>> > >>> > >>> > >>> --- > >>> Incoming mail is certified Virus Free. > >>> Checked by AVG anti-virus system (http://www.grisoft.com). > >>> Version: 6.0.574 / Virus Database: 364 - Release Date: 1/29/2004 > >>> > >> --- > >> Outgoing mail is certified Virus Free. > >> Checked by AVG anti-virus system (http://www.grisoft.com). > >> Version: 6.0.574 / Virus Database: 364 - Release Date: 1/29/2004 > >> > --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: > [EMAIL PROTECTED] > > > > -- > > Gerry Duprey > > ________________________________________ > > SchoolsOPEN, LLC > > 123 North Ashley, Suite 120 > > Ann Arbor, MI 48104 > > Phone (877) 483-1944 Ext. 401 > > Fax (734) 661-0819 > > > > Visit us Online at www.Schools-OPEN.com > > > > > > > --------------------------------------------------------------------- > > 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]
