----- Original Message ----- From: "J Aaron Farr" <[EMAIL PROTECTED]> To: "Avalon Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, November 18, 2003 2:49 PM Subject: Re: [proposal] IoC type 3.14 extension to the Avalon Framework
> Sorry to jump into the thread so late, but I wanted to add a couple of > thoughts: > > - I like the idea of 'Avalon PI' -- I think it's something we should explore. > As Berin mentioned in another thread, we could do this in Fortress without too > much trouble. We could also do it in Merlin, but last I looked at that > section of code it wasn't very flexible (could be wrong now though). > > - A couple of people have already worked on the bridge between Avalon and Pico > components: > Leo Simons in our very own Avalon Sandbox: avalon-sandbox/magic > Plug for my JingDAO framework which uses Picocontainer to handle Avalon, > Pico, and java bean components: http://jingdao.sf.net > I'm sure there are others. I'll take a look at JingDAO. I just checked out Magic in the Avalon sandbox, though It only has one class right now (Avalon2PicoAdapter.java), but it effectively proxies Avalon Framework calls to an IoC type 3 component. It actually (almost) conforms to the Avalon PI proposal! Do great minds think alike or what? :) > > - We need JIRA, or at least a roadmap, in order to keep these proposals from > getting lost while still actually releasing products. I couldn't agree more. > > --- > jaaron <http://jadetower.org> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
