on 12/18/2000 10:45 AM, "Diethelm Guallar, Gonzalo"
<[EMAIL PROTECTED]> wrote:
> The handling of relative files in TR.props is not
> consistent. If you do
>
> include = foo
>
> The file foo is searched for on the same directory where
> the including file (TR.props) is located. However, when
> you say
>
> services.TurbineVelocityService.properties=/WEB-INF/conf/velocity.properties
>
> the file /WEB-INF/conf/velocity.properties is searched
> for from the ServletContext directory (webapp directory).
> Do we really want to have these two cases as different?
> I can see why it makes sense for include to behave the
> way it does (it is similar to what #include "foo" would
> do on C code), but perhaps it should be made to behave
> like V.props does. Or maybe this is not possible, because
> at the point include is processed there is not enough info
> to determine a correct ServletContext object?
Yes, this should be fixed throughout Turbine I think.
First try the path and then try the ServletContext path. Note that it will
tie everything to Turbine.java though so we might want to switch to using
Reflection to attempt to do that.
-jon
--
Honk if you love peace and quiet.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
