> From: Paul Hammant [mailto:[EMAIL PROTECTED] > > > What would that mean? A new constructor? > > In a new class, yes. Nothing about the current API would change. > > > Instinctive -1 based on not wanting to incur promises to remain > > compatible with non-Avalon containers... > > Reconsider? I'll not commti anything that breaks the design > or use of exCornerstone :-)
OK, so it's subclassing + new constructor. I'll retract the -1, but what I'd like is for that subclass to be hosted with PicoContainer, not with exCornerstone. Much like we handled the Log4J adapter for logging -> off to Log4J. Let's see what others think. /LS --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
