>From months of lurking on [EMAIL PROTECTED], I think the biggest change is the way the container deals with singletons. The ThreadSafe marker interface is no longer used as an indicator to make a component/service a singleton. Instead you have to use either the configuration or metadata. I'm not sure exactly which method (or maybe both) fortress uses though...
Age > -----Original Message----- > From: Quinton McCombs [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 11, 2003 19:32 > To: 'Turbine Developers List' > Subject: RE: Avalon container for 2.3 > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 11, 2003 9:37 AM > > To: [EMAIL PROTECTED] > > Subject: RE: Avalon container for 2.3 > > > > > > Could you also supply a list of changes needed in components? > > If ECM is deprecated, I want to update teh HibernateService > > to be Fortress compatiable, and then bring those docs back > > into Turbine. > > I do not know enough about the differences to produce such a > list at this time. After I convert the > AvalonComponentService, I could supply a list to you. > > > Eric > > > > -----Original Message----- > > From: Quinton McCombs [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 11, 2003 10:34 AM > > To: 'Turbine Developers List' > > Subject: RE: Avalon container for 2.3 > > > > > > > -----Original Message----- > > > From: Peter Courcoux [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, June 11, 2003 6:18 AM > > > To: Turbine Developers List > > > Subject: Avalon container for 2.3 > > > > > > > > > Hi all, > > > > > > In case its been missed, the avalon guys have released > version 1.0 > > > of fortress. It occurs to me that with ECM being a deprecated > > > container and fortress now released and, I believe, able > to handle > > > ECM type components, the question should be asked at what > point does > > > turbine switch from ECM. From what I understand fortress > is a good > > > candidate for > > replacing ECM. > > > > Fortress is indeed a good replacement for ECM. I will try to > > get ECM replaced as soon as I have free time from my work > > schedule. I originally went with ECM in the > > AvalonComponentService because Fortress was not released. > > > > > Regards, > > > > > > Peter > > > -- > > > Peter Courcoux <[EMAIL PROTECTED]> > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > --------------------------------------------------------------------- > 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]
