out of curiousity, what happens when you just remove the
file.resource.loader.path (and other file.resource.loader props) and
add no replacements?

i have a feeling that it will work just as it does with them.  (i.e.
without a resource.loader=file property, i don't think the VVS is
using those props at all)

On 4/13/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> My application is likely a common app.  I use it to do both the web dynamic 
> content as well as sending out templated emails out both from Tomcat servlet.
> 
> Previously in 1.4 I was successfully able to specify only the following 
> parameter:
> 
> file.resource.loader.path = /WEB-INF/templates
> 
> Having to specify a full path will be difficult to not make mistakes with 
> moving from development to production just for email templates.
> 
> In development you might have a path like C:/Program Files/Apache Group and 
> in production it would be...different.  Is there an easy way to go off the 
> web base path like with file.resource.loader?  Would make life much easier 
> and less error prone.
> 
> I still need to test to see if that is the problem.
> 
> JohnE
> 
> ---------------------------------------------------------------------
> 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