"Colin Chalmers" <[EMAIL PROTECTED]> writes: >Martin,
>Sounds simple enough. >What should be done with enhancements, should it be done in Turbine or >Fulcrum, both? And is there anything that should be taken into account to >ensure we move closer to Avalon? >I also think you mentioned a preference for releasing more often, what would >be the time frame for 2.3? 3 months? Hi Colin, please be aware that "moving closer to Avalon" to me means: "Make it possible to use our Services from Avalon" in the first place and the in the second place "Check out whether it is possible to replace the BaseServiceBroker with something more slick from Avalon" The first thing means, that we treat our Services as "Avalon Components" and adjust them to the Avalon Lifecycle as described on http://jakarta.apache.org/avalon/framework/reference-the-lifecycle.html This is mainly a matter of renaming some methods and implementing some interfaces from the org.apache.avalon.framework package (Come on people, this is something that _cries_ for a commons package. commons-lifecycle anyone?). There are just a bunch of interfaces with well defined functions that a service must implement. jmcnally started this for Fulcrum which is good. The 2nd part is more tricky as we don't want to overengineer here. The Turbine Service Broker is an overengineered hash table with some init function and you can replace it with something as simple as about 75 lines of code. If we find a small container (which is Avalon Speak for "something that can start up Components") that's cool. If not, I will strip down this glorified bugger into a single class and a single interface which will be able to start up Avalon components in a Turbine manner. (I personally find the following lines on the Avalon web site offensive as this is neither discussed on the Turbine team nor a goal that we all agreed on. And the last sentence basically says "get lost, I do as I want and then I push it on you without discussion. You have no vote on that because it is developed in Plexus-land, not Turbine-land"): --- cut --- http://jakarta.apache.org/avalon/framework/reference-containers.html --- cut --- nPlexus is a container under development that will become the basis of the services framework for a sister project to avalon, Turbine. See Plexus. Plexus is being developed outside of avalon itself as an external project. --- cut --- http://jakarta.apache.org/avalon/framework/reference-containers.html --- cut --- Jason, please remove this from the Avalon website. Or at least the Turbine reference. Regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED] Am Schwabachgrund 22 Fon.: 09131 / 50654-0 [EMAIL PROTECTED] D-91054 Buckenhof Fax.: 09131 / 50654-20 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
