Is using the setPropertiesFileName the proper way to specify the properties
file?

Does it look at web.xml at all?

Matt.

-----Original Message-----
From: Matt Goyer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 21, 2001 4:58 PM
To: [EMAIL PROTECTED]
Subject: RE: TurbineResources.properties


I think I fixed the problem.. I thought specifying
TurbineResources.properties in web.xml was enough.. But I then added a
TurbineResourceService.setPropertiesFileName(..) and it appears to be back
on track.

Should of mentioned I'm using Turbine 2.0.

Thanks anyway,
Matt

-----Original Message-----
From: Jon Stevens [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 21, 2001 4:52 PM
To: Turbine-user
Subject: Re: TurbineResources.properties


on 6/21/01 12:25 PM, "Matt Goyer" <[EMAIL PROTECTED]> wrote:

> We have two different webapps that we're working on.
>
> webapps/app1
> webapps/app2
>
> Both use Turbine and both use different databases. App1 has a
> TurbineResources.properties living in webapps/app1/WEB-INF/conf specifying
> the database it connects to and app2 has it's in
webapps/app2/WEB-INF/conf.
>
> I've specified in app2's web.xml that it should use it's own config but
yet
> time after time app2 is connecting to app1's database instead of it's own.
> It's driving me absolutely crazy.
>
> How can I fix this problem?
>
> Matt

I'm not going to guess the problem. Lets see your settings.

-jon

--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>


---------------------------------------------------------------------
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]

Reply via email to