> From: Leo Simons [mailto:[EMAIL PROTECTED]] > > > I'm in the process of checking the code into Fortress, > and will also > > be checking in the above example into the > > jakarta-avalon-excalibur/fortress/examples directory. > > > > Once the code is checked in, I'm more than open to > suggestions, and > > feedback, so please feel free to fire away with any questions > > (hopefully I or someone else can answer them all!) :) > > mostly, this is pretty cool. > > What I'm not so sure about is whether it satisfies all use > cases. You've defined 4 stages in the component lifetime > where one can register an extension. But what if you want two > extensions in the same stage, in a specific order? >
<SNIP/> If you want to mix and match extension types, there is something wrong in your design. One Extension helper class can support multiple stages in any order you want. Or at least it should be. The concept is simple: provide a callback mechanism to one object. That object can insert any number of stages in a specified order for each callback. This provides an easy way of extending all our containers in a consistent manner. Anything more than that, and I will have to be convinced that it is really necessary. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
