Le jeudi 22 mars 2007 à 09:26 -0700, Nathan Bubna a écrit : > ok, so i started working on this last week, and got further than > anticipated. this week, i've had a little time to refine some things, > so i want to start checking stuff in a bit later today. i've probably > already done more than i ought to have without checking stuff in.
Glad to hear that! > at this point, i'm not thinking extensively about backwards > compatibility, but i do hope to address that eventually. i just > wanted to give a little heads up that some of this stuff is going to > start coming into the 2.x branch today. also, please note that it > compiles with jdk 1.5 and velocity 1.5, but is not yet fully useable > nor have i written tests for the new stuff yet. i do plan to write > tests, and i'm thinking about jdk 1.4 support as well. i'm not > planning to support pre-1.5 Velocity though. > > feedback is welcome, as are contributions. I stay tuned... My daytime job is currently quite demanding, but April should be much more quiet. Oh, responding to one of your previous points: > > i don't see why we need a filter or to constitute the three toolboxes > > at all. It's a need I frequently encountered. Quite simple in fact. If the toolbox manager can be initialized before the view servlet is reached (and for instance from an early filter but the filter itself need not to be provided), then other objects in the webapp (other filters, controller objects) can reach constants and tools defined in the three toolboxes. It just boils down to avoid re-initializing one of the three toolboxes when we read the view servlet. Claude --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
