You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by "Marino A. Jonsson" <ma...@hotmail.com> on 2004/11/02 03:04:21 UTC

Re: Template Caching - IDEA

if you think Tomcat startup is sloooow you might consider taking Jetty for a
spin - it's simply adorable :-)

cheers,
Marin�


"Tim Colson" <tc...@cisco.com> wrote in message
news:200410251534.IAA16722@malone.cisco.com...
> > I've figured out what's going on........
> > I'm using IDEA coupled to Tomcat for my debugging. IDEA
> > creates a deployment
> > directory (exploded) each time you run a debug session,
> Doh. I've run into that too -- in 4.5.1 the exploded dir was required, but
I
> could hit "make" and it just copied the changed template files. In 4.5.2
> however, IDEA seems to also restart Tomcat which is sloooow.
>
> I found that in 4.5.2, you can specify not to create an exploded
directory,
> and use and existing directory instead. So for Velocity integration to
work
> nicely, I have a directory <project>/webapp which has the standard servlet
> dirs (e.g. /WEB-INF) and point the web module config at the web.xml file
at
> /webapp/WEB-INF/web.xml. This means you can edit Velocity templates inside
> IDEA, and see the changes immediately.
>
> Aside -- another benefit of this structure -- with a couple ant tasks, the
> app can be given to an HTML Designer via CVS. After setting up Java &
Tomcat
> on their machine, they can launch the webapp, edit templates, refresh
> browser to see them, and commit changes to CVS. Works great. :-)
>
> Timo




---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org