On Mon, 2002-11-04 at 20:59, Peter Courcoux wrote: > John, > > On Mon, 2002-11-04 at 19:32, John McNally wrote: > > FulcrumContainer is based on ECM. My intention is to use a released > > container and concentrate on converting the individual pieces. I assume > > switching to Plexus or any of the other next-gen containers will be > > reasonably straightforward from there. One possible problem is the use > > of the ThreadSafe interface, which is used with ECM to get > > singleton-like behavior. This matches fairly well with how fulcrum's > > TurbineServices worked. I've seen that this interface is deprecated, > > but I don't know why. > > I believe that the intention is to move towards pluggable lifestyle > handlers declared in component meta-info, but that the embeddable > containers based on fortress and merlin2 will honour the marker > interfaces for lifestyle management.
yep. Threadsafe is a "marker interface", and we've declared those to be the root of limited evil. There will be backwards compatibility though. We've also generally determined the singleton service model is often too limiting...you could read the avalon-dev archives on all that or just ignore that....it works well for most webapps. > I have seen comment indicating that fortress is close to a release! yep. There's not too much work needing doing anymore, but the fortress maintainers are kinda limited on time. > Please note that I'm not an avalon expert and this info is just a result > of too much time reading the avalon lists! you can never spend too much time there :P cheers, Leo -- To unsubscribe, e-mail: <mailto:turbine-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-dev-help@;jakarta.apache.org>
