On Wed, 2002-07-10 at 12:15, [EMAIL PROTECTED] wrote: > In fact, i should have introduced what we've done before, > because I think my questions were a bit vague, and not technical > enough.
=) > > We've developed a medium project (240 classes for the server side) > using Avalon before. We did use ECM to manage the > components (10 roles, 12 implementations). This database-driven > project is technically very advanced as we leveraged powerful > features of the avalon framework. For example, business tasks can be > paused, resumed, stopped, started (with priorities), and so on... All > technical requirements have been met thanks to your work guys. Thanks > for that ! cool =) > But because ECM won't be supported anymore, it'll be supported for some time to come. At least until cocoon switches, I figure... > I'd like to switch new > projects (and the completed one maybe) to its successor which I > believe to be Fortress. yup. Fortress is still alpha though (in the sense that it might change radically, not in that it doesn't work well). > My question about the containers was not about whether I should use > one (Merlin,Fortress,or Phoenix) and what would be > the benefit, it was about why subclassing AbstractContainer in > Fortress :) For example, I didn't have to subclass > ECM to make things work. I talked about the examples of Marcus because > he did subclass AbstractContainer for each example : > servlet example, and swing example. > > My concerns were about the best practices when using Fortress, not about > whether I should use it or not ;) I'd say no. Create one, use it in all your different contexts. Then again, I didn't write fortress. cheers, - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
