You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by Ken Corey <Ke...@sportal.net> on 2000/10/31 13:24:31 UTC

Mailing list Archive?

Hi All,

Sorry for the wide distribution.  Is there an Archive for this list?  I
can't see one mentioned.  'RTFM' type comments are appreciated, as long as
there's a pointer to the 'M's...

When I went to the FAQ-o-matic (I actually got it to work! Yay!) it didn't
mention Velocity.

The installation instructions talk about building velocity, but they don't
seem to talk about integration with Tomcat and or Apache.  Is this
possible/easy?  How about with jserv?

Why was Velocity created when webmacro existed? Is it in a state suitable
for use in place of webmacro? Is there some compelling reason (in a
multi-apache, multi-jserv environment) why I should go with Velocity rather
than WebMacro?

Curious minds and all that.

Thanks.

-Ken

Re: Mailing list Archive?

Posted by Rafal Krzewski <Ra...@e-point.pl>.
Ken Corey wrote:
> Sorry for the wide distribution.  Is there an Archive for this list?
> I can't see one mentioned.  'RTFM' type comments are appreciated, as
> long as there's a pointer to the 'M's...

I don't know about one, but it's fairly probable that it exists
somewhere.

> The installation instructions talk about building velocity, but they
> don't seem to talk about integration with Tomcat and or Apache.  Is
> this possible/easy?  How about with jserv?

It's possible to use Velocity in any Java application, not necessarily
related to the web/servlets. You can use it to generate SQL/Java
sources/
XML or anything that has textual form.

I believe that there is some kind of framework, similar to those in
WebMacro
that allows to build a simple web application using Velocity as the
controlling
Servlet, and providing your own templtes/objects. I didn't look closer
at
the sources yet ;-)
For more complex applications you should consider using Turbine, which
already
has support for Velocity next to WebMacro, and Velocity is going to
become
the default templating package for Turbine in the future.

> Why was Velocity created when webmacro existed? Is it in a state
> suitable for use in place of webmacro? Is there some compelling reason
> (in a multi-apache, multi-jserv environment) why I should go with
> Velocity rather than WebMacro?

The main reason for creation of Velocity was license problems with
WebMacro,
and problems in communication/cooperation that happened between Justin
Wells
(WebMacro creator) and members of Turbine project. Other than that, the
rewrite was hoped to bring technical improvement, like new approach to 
template parsing (JavaCC instead of hand-written) and removal of certain
things considered overengineering in WebMacro by the interested
developers.

Right now, Velocity has a team of active developers, and the works are
progressing nicely. It's already usable, and we expect that it will
supersede 
WebMacro both in features, stability, performance and eventually user
base.

Rafal

--
Rafal Krzewski
Senior Internet Developer
mailto:Rafal.Krzewski@e-point.pl
+48 22 8534830 http://e-point.pl