I don't think it's server-specific.
After looking at VelocityManager code, one can see that there's a few possible ways of
configuring it:
/**
* if the user has specified an external velocity configuration file, we'll
want to search for it in the
* following order
*
* 1. relative to the context path
* 2. relative to /WEB-INF
* 3. in the class path
*/
So, there are all of these choices.
I just described what worked for me and I think having it in WEB-INF is the most
confortable,
since you can change it, without needed to 're-build'.
I wanted to add this to wiki, but I'm having problems retreiving my password.
It says It will send me password to email, but I'm getting nothing.
I'm almost sure, I provided an email when I registered.
Anyone can check this?
user: fmar
email:[EMAIL PROTECTED] OR [EMAIL PROTECTED]
Thanks
Fernando Martins
On Tuesday 03 February 2004 04:45, Drew McAuliffe wrote:
> Again, I've had success without putting any properties in WEB-INF. I put
> everything in the classpath (under "WEB-INF/classes") and everything works
> for me. The key was referencing my velocity.properties file from my
> webwork.properties file. This is on Oracle oc4j and orion 2.0, so if you're
> experiencing something different, it might be server-specific and would be
> useful to know.
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Fernando Martins
> Sent: Monday, February 02, 2004 12:32 PM
> To: [EMAIL PROTECTED]
> Subject: Re: AW: AW: [OS-webwork] Velocity Template caching
>
>
> Make sure:
>
> 1) you DON'T have (or have it comment out) in your velocity.properties:
> resource.loader = <whatever>
> because if VelocityManager finds an already configured resource.loader it
> will not set the templates.path.
> 2) you load the WebWorkVelocityServlet in your web.xml (this is a little
> stupid, because if one doesn't want to use velocity directly, this should
> be necessary. But otherwise I was not able to get my velocity.properties
> loaded)
> 3) you have velocity.properties in WEB-INF.
> 4)
>
> >wwfile.resource.loader.cache = true
> > wwfile.resource.loader.modificationCheckInterval = 10
>
> This works for me. I hope I didn't forget any detail.
> Please confirm that this works, so that finally we could put it in the
> Cookbook on the wiki or somethig.
>
> Fernando Martins
>
> On Sunday 01 February 2004 14:59, Hans Prueller wrote:
> > sorry for that.. but it also doesn't work! even if i try both
> > configuration ways
> >
> > file.resource.loader.cache = true
> > file.resource.loader.modificationCheckInterval = 10
> >
> > wwfile.resource.loader.cache = true
> > wwfile.resource.loader.modificationCheckInterval = 10
> >
> > if i change a velocity template, the changes are immediately visible,
> > not after 10 seconds so I guess it doesnt work..
> >
> > hans
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] Im Auftrag
> > > von Dag Liodden
> > > Gesendet: Sonntag, 01. Februar 2004 13:36
> > > An: [EMAIL PROTECTED]
> > > Betreff: Re: AW: [OS-webwork] Velocity Template caching
> > >
> > > As I mentioned in a recent post, velocity.properties needs to be in
> > > WEB-INF. :)
> > >
> > > Dag
> > >
> > > Hans Prueller wrote:
> > > >in my case, it didn't work... i tried to use
> > > >wwfile.resource.loader.cache = true
> > > >wwfile.resource.loader.modificationCheckInterval = 10
> > > >
> > > >in webwork.properties AND in a velocity.properties file in
> > >
> > > classpath..
> > >
> > > >if I modify a template, the changes are immediately visible.
> > >
> > > do I need
> > >
> > > >a newer version of WW2 than beta2 ???
> > > >
> > > >hans
> > > >
> > > >>-----Ursprüngliche Nachricht-----
> > > >>Von: [EMAIL PROTECTED]
> > > >>[mailto:[EMAIL PROTECTED]
> > >
> > > Im Auftrag
> > >
> > > >>von Fernando Martins
> > > >>Gesendet: Samstag, 31. Jänner 2004 18:59
> > > >>An: [EMAIL PROTECTED]
> > > >>Betreff: Re: [OS-webwork] Velocity Template caching
> > > >>
> > > >>On Saturday 31 January 2004 13:22, Fernando Martins wrote:
> > > >>>wwfile.resource.loader.cache = true
> > > >>>wwfile.resource.loader.modificationCheckInterval =
> > > >>><some_interval>
> > > >>>
> > > >>>I don't know if this will work, I'll give a try, and let you know.
> > > >>
> > > >>I tried this, and it seems to be working.
> > > >>So after all is quite easy to turn on velocity template caching in
> > > >>ww2.
> > > >>One just needs to add these 2 lines to velocity.properties:
> > > >>
> > > >>wwfile.resource.loader.cache = true
> > > >>wwfile.resource.loader.modificationCheckInterval = <some_interval>
> > > >>
> > > >>This should speed up things quite a bit, when using File resource
> > > >>templates.
> > > >>
> > > >>This information should be available in some place in the
> > > >>documentation/wiki.
> > > >>If some of the core developers be so kind to add it or at
> > >
> > > least to say
> > >
> > > >>where it should be added.
> > > >>
> > > >>thanks
> > > >>Fernando Martins
> > > >>
> > > >>
> > > >>
> > > >>-------------------------------------------------------
> > > >>The SF.Net email is sponsored by EclipseCon 2004 Premiere
> > >
> > > Conference
> > >
> > > >>on Open Tools Development and Integration See the breadth
> > >
> > > of Eclipse
> > >
> > > >>activity. February 3-5 in Anaheim, CA.
> > > >>http://www.eclipsecon.org/osdn
> > > >>_______________________________________________
> > > >>Opensymphony-webwork mailing list
> > > >>[EMAIL PROTECTED]
> > > >>https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> > > >
> > > >-------------------------------------------------------
> > > >The SF.Net email is sponsored by EclipseCon 2004 Premiere
> > >
> > > Conference on
> > >
> > > >Open Tools Development and Integration See the breadth of Eclipse
> > > >activity. February 3-5 in Anaheim, CA.
> > > >http://www.eclipsecon.org/osdn
> > > >_______________________________________________
> > > >Opensymphony-webwork mailing list
> > > >[EMAIL PROTECTED]
> > > >https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> > >
> > > -------------------------------------------------------
> > > The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference
> > > on Open Tools Development and Integration See the breadth of Eclipse
> > > activity. February 3-5 in Anaheim, CA.
> > > http://www.eclipsecon.org/osdn
> > > _______________________________________________
> > > Opensymphony-webwork mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> >
> > -------------------------------------------------------
> > The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference
> > on Open Tools Development and Integration See the breadth of Eclipse
> > activity. February 3-5 in Anaheim, CA.
> > http://www.eclipsecon.org/osdn
> > _______________________________________________
> > Opensymphony-webwork mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
>
> --
> "Everywhere is walking distance if you have the time" - Steven Wright
>
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Opensymphony-webwork mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
--
"Everywhere is walking distance if you have the time" - Steven Wright
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
