Leo Sutic wrote: <snip/>
> Instead of trying to be the "do everything", the ultimate > dependency, the framework for *all* of Jakarta, we would > release framework 4.0, Excalibur 4.0, and then not consider > A5 an upgrade, but something entirely new. The A4 architecture > would still be 100% supported not as a deprecated product, > but as a 100% alive and kicking architecture. What if.... it was possible to write a component handler (ContainerKit?) that was responsible for calling all the lifecycle methods on a component e.g. LifecycleHelper.startup(), so that you never needed to call a components lifecycle methods directly... and give this handler a well defined API -- so that whenever you wanted to use a component (or a container wanted to use a component) you would use this component handler API... then you could give the framework a complete overhaul and only need to update the component handler for everything to keep working -- you could have A5 components beside A4 components, only the component handler would know the difference... maybe what is needed is two frameworks... One framework to write components (the current framework), and one framework to use the components (the component handler API)... these could evolve semi-independantly and the component handler implementation could be a bridge between them. Robert. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
