On Fri, May 2, 2008 at 11:55 AM, csanders <[EMAIL PROTECTED]> wrote: > > > are you deploying to a servlet container? if so, then the > > FileResourceLoader is not your friend. you should be using the > > WebappLoader (aka WebappResourceLoader) that is part of the > > VelocityTools project. It uses servlet context relative paths. > > > > Ahh cool, Ill check that out. I know you're the author so its hard for you > to present an unbiased view but are there any penalty performances moving > to this loader ?
oh, and while Claude and i have done some tweaking on the WebappLoader, Geir was the original creator. :) > > > > > i don't think it would be all that hard to add support for including> > > environmental variables in the properties. you would pretty much just > > watch for properties either coming in or going out of RuntimeInstance > > for environment variables and do the replacement there. It would > > probably be easiest to do this in RuntimeInstance#getProperty. > > > > Ok thanks. > > Thanks Nathan, > Charlei > > > > > > Nathan Bubna wrote: > > > On Fri, May 2, 2008 at 7:50 AM, csanders <[EMAIL PROTECTED]> wrote: > > > > > > > Is there anyway we can set relative paths in this file ? > > > > > > > > > > in which file? in velocity.properties? > > > > > > > > > This is the only configuration file out of dozens that doesn't support > this and its making deployment a serious pain. > > > > > > > > > > > > > are you deploying to a servlet container? if so, then the > > FileResourceLoader is not your friend. you should be using the > > WebappLoader (aka WebappResourceLoader) that is part of the > > VelocityTools project. It uses servlet context relative paths. > > > > > > > > > Or can I use environmental variables in this file ? That would work > also. > > > > > > > > > > > > > sounds like a useful thing to me! > > > > > > > > > If not - how much development would it take to get this to work ? It > might be worth it for us to contribute this to Velocity. > > > > > > > > > > > > > i don't think it would be all that hard to add support for including > > environmental variables in the properties. you would pretty much just > > watch for properties either coming in or going out of RuntimeInstance > > for environment variables and do the replacement there. It would > > probably be easiest to do this in RuntimeInstance#getProperty. > > > > > > > > > > > Thanks, > > > Charlie > > > > > > --------------------------------------------------------------------- > > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
