> I'd love to see more components which separate interface and > implementation. Ideally, they could have multiple interfaces. One per > framework. Each sharing a common(s) implementation.
YEah, IMO Paul is doing it (in one of) the right way(s). I hope the rest of Avalon-Phoenix follows! =:o) Have fun, Paulo > -----Original Message----- > From: Sam Ruby [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 21, 2002 9:20 PM > To: Jakarta Commons Developers List > Subject: Re: AltRMI Tasks if anyone want to take them > > > Paul Hammant wrote: > > > > OK, a quesiton. Commons is about "beanlike" classes that have multiple > > reuse in servers (though client is not precluded). Avalon-Excalibur is > > about reusable components that fit the IoC pattern, and in the context > > of Avalon are decorated at startup from XML configuration, to do this > > quite a few of them site of Avalon-Framework's componenet abstractions. > > That a (my) simple view. > > > > I've tried to code AltRMI so that is usable in the context of an XML > > configurable component env like Avalon-Phoenix. It's quite easy if you > > <boredom-alert> rigidly separate interface and impl </boredom-alert>. > > Of course I could have got it quite wrong... Thus in my view AltRMI is > > beanlike but because of it's interface/impl separation, it can fit the > > Avalon-Phoenix env too. I can't help feeling that I have forgotten > > about the needs of my Excalibur buddies. > > Parse error. Question not found. :-P > > I'd love to see more components which separate interface and > implementation. Ideally, they could have multiple interfaces. One per > framework. Each sharing a common(s) implementation. > > - Sam Ruby > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
