Schnitzer, Jeff [EMAIL PROTECTED] writes:
Velocity produces text that must be parsed to perform XSLT transforms.
This new approach starts immediately with SAX events. Unlike a
hypothetical saxify, it doesn't require fully navigating the source
object graph. Cool.
yes, I think so too. in
developpers think harder about their added value in open source space.
Eelco
- Original Message -
From: Joseph Dane [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, August 27, 2004 9:24 PM
Subject: Re: [Mav-user] a new view
Doug Kirk [EMAIL PROTECTED] writes:
Hmmm...I don't want
Hmmm...I don't want to rain on any parades, but I'm just wondering why
you didn't want to use Velocity, as it accomplishes the same thing and
it's already written and well-supported?
--doug
---
This SF.Net email is sponsored by BEA Weblogic
It sound nice. I use Velocity mostly, and am still very content with it.
But, Velocity would not be useful for you as it does not provide you with
valid XML source files. Just wondering... what kind of stuff are you doing
with these XML input files?
Eelco
- Original Message -
From:
Doug Kirk [EMAIL PROTECTED] writes:
Hmmm...I don't want to rain on any parades, but I'm just wondering why
you didn't want to use Velocity, as it accomplishes the same thing and
it's already written and well-supported?
I do use Velocity, and am happy with it in the contexts in which I
use it.
