While I unfortunately don't presently have time to contribute towards testing this, backporting the pipeline from t3 to t2 is a great step forward.A key enhancement to Turbine 3 was the "Pipeline". This basically changed the stages of processing of a doGet/doPost to be based on a series of Valves that you could define in an XML file. This allows you to change the order of processing of a doGet so that if you have a custom piece of validation, you can just add another Valve. Or, if you don't use parts, then you can remove those valves that you don't need.
I took the T3 code on org.apache.turbine.pipeline and backported it to work with 2.4. So far I have tested it in my fairly complex Turbine app, and it all looks good. I took the approach of just using the T3 valve architecture, everything else is T2.4 specific, so it should be perfectly backwards compatible. Therefore things like branching logic etc in the Valves I ignored.
I'd love to get some feedback on this from people. If you find a bug, add a test case to the unit tests...
Incidentally, weren't the pipeline and externalisation of services supposed the big pluses to be gained from t3? I'm curious to know how far apart these two are now (of course the big negative for t3 is that there is no real development going on).
Are you working on a migration path for t3 apps back to t2? It seems like this may soon be possible.
Good stuff!
Scott
-- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
