Jon Stevens wrote:
>
> on 12/18/2000 12:21 PM, "[EMAIL PROTECTED]"
> <[EMAIL PROTECTED]> wrote:
>
> > An alternate way to provide consistent file and URLs definition
> > in TR.p is to let the Resources service itself resolve the relative
> > paths and URL to absolute references at runtime, so that you can
> > write:
> >
> > include =${conf.dir}/myproperties
> > properties=${webapp.dir}/WEB-INF/conf/myproperties
> > etc.
>
> Actually, I think that you shouldn't have to write the ${conf.dir} stuff at
> all. If you are going to let the ResourceService deal with it, then it
> should add it in for you. All of the paths should just be treated as
> relative to the Context App root.
>
> I'm -1 on adding in ${conf.dir} expansion as it just isn't needed.
>
It was just an example.
In any case this would not work for the include directive because it's
handled directly by the ExtendedProperties class when the properties
file is loaded.
--
Rapha�l Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
