On Saturday 15 March 2003 05:54, Stephen McConnell wrote: > Stefano Mazzocchi wrote: > > Stephen McConnell wrote: > >> Niclas Hedhman wrote: > >>> Hooahh, and how much of that will affect me, just starting to > >>> migrate my "legacy" application to Avalon-Phoenix?? Not at all? A > >>> little bit? > >> > >> Please note that the comments express by Peter Donald should in no > >> way be considered as a position of this community or in any way > >> reflective of the community consensus. > > > > I think everybody around apache knows that and Niclas has been around > > for enough time to know this very well. > > Please excuse my ignorance. I have not had the opportunity of meeting > Niclas Hedhman on-line or off. From his comments it was apparent to me > that he considered the comments and opinions as expressed by Peter > Donald's as in some way or form an indication of the community opinion. > My response was provided with the objective of reassuring Niclas Hedhman > that the Avalon Community has not taken any such decision. I would like > to reassert the point that the opinions stated by Peter Donald are his > own and should not be interpreted in any way or form as a reflection of > the opinions of the Avalon Community at this time.
So here I am. You met me ONline... Stefano knows me for being a loud and critical ba***rd at the Cocoon list. Well, I know that individuals are still individuals in a community, but I interpreted 2 things in Peter's message + one from other messages surrounding Merlin; 1. The changes were a roadmap of what to do next. 2. "Implied" that a lot of "dead meat" is going to be cut away, and new "dead meat" to be defined. 3. Phoenix future may be a deprecation into Merlin. Also, Stefano has been fairly "loud" about Cocoon's dependency on Avalon, and Avalon was a "moving target", continiously creating problems in the Cocoon camp. That's part of my baggage coming here. BTW, I managed the conversion ( Phase I ) of my Process Control framework into a Phoenix server in just over 2 days (+4 hours of studying Avalon in papers). Steps that were taken; 1. Introduced a new class, implementing a bunch of Avalon interfaces, and coping the "startup code" from the old bootstrapper. And a .xinfo file for this block. 2. Moved some code around in that class. 3. Change in the build.xml 4. Changed the code for establishing ProductRoot and ProjectRoot dirs. 5. Created a new "legacy Logger" class, and let the "LoggerFactory" serve it, mapping old logs to Avalon Logger. 6. A separate project for the SAR assembly. Killed off one text file in favour of config.xml. That's it. Phase II is starting next week, where the legacy services will be transformed into Avalon Blocks. And the legacy stuff should be just as easy as the "whole app", since they follow the same "similar" life cycle as Avalon has in place. I AM VERY PLEASED!!!! Thanks to everyone who has brought Avalon-Phoenix this far, although reading this list over the last couple of days, I must say you quabble(?) a lot. Cheers. Niclas P.S. Stephen - You really enjoy writing emails, don't you ;o) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
