Hi Peter,
regarding the decision of choosing an Avalon container
+) ECM is dead
+) Merlin/Metro was never intended as embeddable Avalon container hence the problem with embedding it
+) Fortress is a valid choice but requires some work
+) YAAFI is used for Fulcrum builds the last 6 months
Having said that
+) there is no need to deprecate ECM based services since they all run with YAAFI
+) we use YAAFI and Fulcrum in production for serveral products now
Cheers,
Siegfried Goeschl
Peter Courcoux wrote:
Siegfried,
I think Eric Pugh and myself were the last people to work on the 2.4 codebase. As far as I am concerned one major issue remains which is that we are still using ECM as the container for Avalon style components. I think that we need to make a decision on which container to use and then embed it, deprecating the ECM based service. I know lots of work has been done on YAAFI but have not looked at it myself. Is this a reasonable option? I have lost track of Fortress but this was the option we were favouring when we last had time to look.
As an aside, have you seen this :- http://www.theserverside.com/articles/article.tss?l=IOCandEJB
There is some work to be done in continuing the refactoring of the RunData interface and implementation. I would like to effectively replace RunData with PipelineData but keep a deprecated RunData option for backwards compatibility. I'm not sure how long this would take but I don't think it is too much work.
That said, I have 2.4 in use in production, and it seems stable.
I agree with you it would be nice to work towards a release.
I'm at home at the moment so I'm not always at my desk, but I am periodically on #turbine irc channel if you want to chat.
Eric, do you have anything to add?
Regards,
Peter
Siegfried Goeschl wrote:
Hi folks,
are there any plans for a Turbine 2.4 M2 release?! Personally I would like to use the Fulcrum components instead of Turbine components ... :-)
Cheers,
Siegfried Goeschl
--------------------------------------------------------------------- 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]
