Vadim Gritsenko dijo: >> Hmm, I actually don't know what's best. What do others think? > > The best plan IMHO would be: > > 1. Remove ECM - implementation of Avalon container. Keep re-usable > components > code (XSLT, Source, Store, etc). > 2. Drop in the container which replaces it. > 3. Write bridge code between container in (2) and (1). > 4. Test. > 5. Release Cocoon 2.3. > 6. Continue with usual Cocoon development: improvements, refactorings, as > you > see fit: rewrite source resolving or sitemap processor or whatever you > want if > you have time for it. > > For a useful example of 6, Store implementation should plug in into Java > 1.5 > management API instead of having background checker thread.
I guess the sample of 6 is just a sample. If not that means we will target as minimum to java 1.5. Anyway, I like this plan. ;-) Best Regards, Antonio Gallardo
