> -----Original Message----- > From: Alex Karasulu [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 10, 2004 1:08 PM > To: 'Avalon Developers List' > Subject: RE: Yet another IoC Article > > Hi, > > > Anyway, you brought up two good points: > > > > 1. Support of other dependency management schemes in Avalon > > 2. Making it easier to reuse Avalon components in non-Avalon frameworks > > I really would like to do away with this approach here > > http://incubator.apache.org/directory/subprojects/eve/components.html > > to make Eve's components available to other containers like Pico. > > It would be nice to pick a container without this sort of run-around > to make components interoperable within multiple containers. > > Also if others have any novel approaches regarding a means to make > components container neutral please let me know. > > I'm really hoping Avalon PI will become a reality. > > Alex
Look at the source in my "Mutuals" example at http://www.jadetower.org/spire/mutuals/ I still need to update some of it, but it shows how I handle writing components for both Fortress and PicoContainer. Basically, what I do is write all the non-framework related code in an abstract implementation and then write a simple Fortress, Pico or Merlin implementation. With a little planning this should be very easy to do. It's not perfect, but it's one approach. J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
