The attached diff will show how we can use the Event package which is a released product instead of the Cornerstone JARs for the same purpose.
Will Avalon keep supporting both? I mean, which one is the *official* one.
We have the added benefit of knowing that we can access the Event stuff via the same mechanisms when (and if) Cocoon migrates to using Fortress instead of ECM.
Ah, I see.
It is pretty easy to use, and we are trading a requirement for four jars to a requirement for one.
Cornerstone-Thread requires Excalibur Thread and Excalibur ThreadContext Cornerstone-Scheduler requires Cornerstone-Thread.
Event (in its current incarnation) has all the functionality under one roof. It also has a vastly improved pooling mechanism, but that is another excersize completely.
If you think its a good idea, I can make the commit...
I see nothing wrong, +1 from my side.
-- Stefano Mazzocchi <[EMAIL PROTECTED]> Pluralitas non est ponenda sine necessitate [William of Ockham] --------------------------------------------------------------------
