Rafal Krzewski wrote:
>
> It just makes me worried, that parser problems still keep showing up.
> I'm affraid that we'd get tons of Velocity related issues if we
> start to use it at a large project. For example http://pfm.pl has
> 1.8MB of WebMacro markup in 450 files and http://www.wbksa.pl has
> 1MB in 300 files. We started those before Velocity was available,
> and we aren't going to port them just right now...
The problems that show up are generally related to one root cause. I
have done some preliminary work investigating the solution, but didn't
want to do anything until after release 1.0. It's a biggie.
I have a client where quite a few in Vel, converted from WM (I don't
know the count).
I have another who produces all content dymically via XML/XSLT, and are
able to use Velocity parsing of dynamically generated streams in
realtime - there isn't even templates that we can check for
'correctness' for the most part. There are a few top level ones, but
the rest is dynamic - I have VTL embedded in XSL, even, for the parts we
haven't converted to Anakia-like XML styling. :)
All works like a charm.
I base part of my living and reputation as a consultant on it these
days...
>
> Please don't take me wrong. We'd love to use Velocity, but we are
> anxious how it will work for us.
>
We'd love to see you use Velocity, and are anxious how it will work for
you.
:)
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
