On Sun, 2005-03-13 at 09:46 +0000, robert burrell donkin wrote: > On Sun, 2005-03-13 at 10:40 +1300, Simon Kitching wrote: > > > > And besides, commons-logging and commons-beanutils and similar don't > > just need to work in j2ee-compliant frameworks; they need to work in all > > *real-world* frameworks. And as can be seen from replies to my earlier > > question about parent-first vs child-first classloading, popular tools > > such as Resin and Websphere provide deployment options that violate the > > j2ee spec anyway. > > +1
I'm wondering if we need to provide a configurable "Singleton strategy" that the user of the library can set. We would provide a default "singleton strategy" but users could override that if the default behaviour doesn't result in correct Singleton behaviour. I'm actually wondering if we actually need a simple commons-singleton library that other libs would use. Commons-logging and commons-beanutils certainly could use it; I'm betting that other commons libs have attempts at implementing singletons that don't work. The major problem I forsee with this suggestion is that commons-singleton configuration (eg user-specific strategy) is probably best stored as a Singleton :-(. Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
