> My point is that componentization was not a design goal of Turbine to begin > with and trying to retrofit it in the framework will take a *huge* amount > of effort. My original intention was to use the ideas of Avalon, not use Avalon itself. I would like to make the services of Turbine pluggable, use JAR files and provide a way to configure services that are dynamically added to the system. My original intent was never to make services directly compatible with Avalon. That might be a good idea but not what I was going to initially try to implement. jvz. ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
- Re: Turbine Release Daniel Rall
- Re: Turbine Release Jon Stevens
- Re: Turbine Release Jon Stevens
- Re: Turbine Release Jason van Zyl
- Re: Turbine Release Jon Stevens
- Re: Turbine Release Daniel Rall
- Re: Turbine Services as plugins Rafal Krzewski
- Re: Turbine Services as plugins raphael . luta
- Re: Turbine Services as plugins Rafal Krzewski
- Re: Turbine Services as plugins raphael . luta
- Re: Turbine Services as plugins Jason van Zyl
- Re: Turbine Services as plugins John Thorhauer
- Re: Turbine Services as plugins Jon Stevens
- Re: Turbine Services as plugins Rafal Krzewski
- Re: Turbine Services as plugins Jon Stevens
- RE: Turbine Services as plugins Chris Campbell
- Re: Turbine Services as plugins raphael . luta
- RE: Turbine Services as plugins Chris Campbell
- Re: Turbine Services as plugins Daniel Rall
- Re: Turbine Services as plugins Jon Stevens
- Re: Turbine Services as plugins Jon Stevens
