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?
Just curious,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
