Re: "parse" directive in velocity template failing

2008-01-22 Thread James McLaughlin
fattymelt, yes that looks right. This used to work. I will try to get some time later today to see what is going on. There should be a velocity.log somewhere that could be helpful. wicket-velocity has an Initializer that searches for and loads the properties file, so set a breakpoint in init to see

Re: "parse" directive in velocity template failing

2008-01-22 Thread fattymelt
Thanks for the help, James. I tried adding the following to my web.xml (and putting the velocity.properties file in that location). Does this look right to you? ClientApplication wicket.protocol.http.WicketServlet applicationClassName com.foo.bar.

Re: "parse" directive in velocity template failing

2008-01-22 Thread James McLaughlin
On Jan 21, 2008 11:45 PM, fattymelt <[EMAIL PROTECTED]> wrote: > > Just to be sure... > > In the Wicket section of web.xml I am going to add the two init-params. One > of which defines the folder in which to find my properties file, and the > other is the actual filename. Then I can use that proper

Re: "parse" directive in velocity template failing

2008-01-21 Thread fattymelt
Just to be sure... In the Wicket section of web.xml I am going to add the two init-params. One of which defines the folder in which to find my properties file, and the other is the actual filename. Then I can use that properties file to specify what my TEMPLATE_ROOT is. The only I don't get, is

Re: "parse" directive in velocity template failing

2008-01-21 Thread James McLaughlin
fattymelt, It used to work that you could jar up your templates and put them under WEB-INF/lib. If that doesn't work, create your own velocity.properties file and define the init-params velocityPropertiesFolder and velocity.properties in your web.xml. You can define there which loaders to use and w

"parse" directive in velocity template failing

2008-01-21 Thread fattymelt
I am using a velocity template, and within it would like to use velocity's "parse" directive (to include another template within the current template) but it complains that it can not find the template in velocity's "TEMPLATE_ROOT." I have triple-checked that the template is in the same directory