Hi All (especially Geir :-),
Thanx for the effort!
I tried Velocity v1.1-rc1 and it seems to be working fine with a relatively
complex XML based app.
I've been testing it for a while and all seems well (including
EventCartridges, recursive #macro, complex context objects and so on).
Speed seems to be on par with previous versions.
~ Leon
----- Original Message -----
From: "Geir Magnusson Jr." <[EMAIL PROTECTED]>
To: "velocity-dev" <[EMAIL PROTECTED]>; "velocity-user"
<[EMAIL PROTECTED]>
Sent: Monday, May 21, 2001 3:11 AM
Subject: Velocity v1.1-rc1 released
> Congratulations, everyone -
>
> The 1st release candidate of version 1.1 of the Velocity Template Engine
> is now released.
>
> Major enhancements include :
> - The new event-handling facility, allowing finer control and
> interaction with the rendering process.
> - Internationalization support through full support of template
> character encoding.
> - Optimizations for improved performance.
>
> There are many minor enhancements as well.
>
> -----
>
> There is now a separate v1.1 branch, as I learned my lesson last time :)
>
> There are a few *important* changes in the CVS :
>
> 1) the event handling stuff was moved from
>
> org.apache.velocity.context
>
> to
>
> org.apache.velocity.app.event
>
> so you must change your import statements.
>
>
> 2) The NullSetEventHandler was changed - the method the interface
> defines was changed from :
>
> public boolean nullSetEventLogMessage( String reference )
>
> <or something like that>
>
> to
>
> public boolean shouldLogOnNullSet( String left, String right )
>
> which seems to be more descriptive. if you don't like this, we still
> can change. I also added the second arg, so you can see what the LHS
> and the RHS are for a #set(). Figured it couldn't hurt.
>
> 3) Added a new switch for logging -
>
> resource.manager.logwhenfound = true
>
> will, when changed to false, will stop the log messages when a resource
> is found. The default, of course is true, and not this will only log
> the the first time a resource is accessed when caching is on, so
> shouldn't require a change to most production installations.
>
> geir
>
> --
> Geir Magnusson Jr. [EMAIL PROTECTED]
> System and Software Consulting
> Developing for the web? See http://jakarta.apache.org/velocity/
> "still climbing up to the shoulders..."
