----- Original Message ----- From: "Leo Simons" <[EMAIL PROTECTED]>
<...> It may be not a standard yet, but lets be practical: how to make it standard? My suggestion: - The current builder package (in impl) should move to Merlin. - Fortress should implement its own Builder based on what is actualling doing for service/components. - Any other container should follow the same path. The current Builder implementation is Merlin specific - and I agree should not be considered an Avalon standard. However the Meta package describes the flesh and bone of an Avalon component/services and related facilities. So its a good idea to use it an standard (I port it to .Net right this time and notice how its supress strategies I already made in my first container implementation) Instead of pointing fingers to each other lets do what is necessary to do to make things works as we expected - or at least think it is the desired behavior. What about the XP practices in Avalon ? :-) regards, hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
