Steve, Pete, Paul, if you ask me, Paul is right with regard to the seperation of spec and default impl -- putting it at the jar level is nice, and consistent with A-F.
Also, I don't think the excalibur container package should neccessarily be limited to only default impls of the client side; it's very name implies it is also about the other side, doesn't it? Next, I think putting the classes in the container package sort-of 'forces' more convergence between merlin and fortress as the container package is sort-of common ground. Which I like ;) And when that convergence happens, there is nothing to prevent modification of the classes in container to match the changed implementation. right? Finally, I think regardless of all that I like the setup that will be quickest to get fortress to release quality best, if that matters in any direction. I'm very happy to see Pete work on fortress :) cheers, - Leo -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
