I've been banging my head against the type-1/2/3 split for some time now. I started porting my applications to PicoContainer, which is a pain-in-the-you-know-where because Pico hasn't got the avalon-style release() semantics. So I wrote a type-1/2/3 container:
http://jicarilla.sourceforge.net/ http://cvs.sourceforge.net/viewcvs.py/jicarilla/jicarilla-sandbox/platform/container/
The next step was some proof-of-concept integration with pico*:
http://cvs.sourceforge.net/viewcvs.py/jicarilla/jicarilla-sandbox/platform/container/impl/src/test/com/leosimons/jicarilla/container/integration/pico/
that's coming along nicely, though it's rather ugly. I had a hunch that avalon integration would actually be simpler. The results so far can be seen at*:
http://cvs.sourceforge.net/viewcvs.py/jicarilla/jicarilla-sandbox/platform/container/impl/src/test/com/leosimons/jicarilla/container/integration/avalon/
I have a very basic implementation of the Fortress Container interface running. The next step will be creation of a frontend (ContainerManager implementation) that reads the fortress configuration formats. I will likely be writing a fortress TCK as I implement support for it. Unless I get bored.
Anyway, may be of interest to some since some things are done quite differently.
happy new year!
- LSD
* will show up here after what's roughly a 24-hour delay because of the SF CVS server crap
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
