On Fri, 2002-10-18 at 13:31, David Worms wrote: > i am using turbine 3 and fulcrum successfully, but i really don't mind > if we drop turbine 3. my turbine and fulcrum jar are stable and will > continue to be in the future for the needs of my current application. > plexus looks great, i just made the sample app running yesterday.
I think with very little effort any Fulcrum service can be turned into an Avalon one. In addition the Avalon lifecycle is richer and can only serve to enhance any Fulcrum service. I specific example is being able to restart a service without having to shut everything down. With Tambora I know that we have had a nightmare with clients who are "not-so-with-it" and trying to get them to do anything with the server has proven to be a complete waste of time. For Tambora we need to be able to tweak things while the system is running and make any sort of modifications without restarting everything. I'm sure this many people require this and is the way Summit/Plexus will work. At this point Summit is stored with the other Plexus components but it is still a hybrid at this moment. Also note that Summit apps only run inside Plexus with Jetty. This will be easy enough to change but I'm just warning people not to expect too much right this second. We are shooting for a release of Tambora early in the new year and we can hire people if we feel it will aid in the development so everything will be working in short order. What's coming: o Maven plugin to build a Plexus installation o Maven plugin to build a Summit app o Fully functional OJB component o Full JMX management Just to name a few things. There are pieces of all the above already started but as mentioned in a previous email the OJB and JMX aren't there. I will see if I can get the tambora 3 site out in the open (we've been keeping it private for various reasons) which outlines a lot of the functionality we need and when we have things scheduled for completion. We are using Scrum (http://www.controlchaos.com) and our next 30 day sprint focuses more on Tambora specific issues but I will be putting in my own time to get Plexus and Summit working in general. In subsequent sprints Plexus and Summit will get full attention. I also see from the poll that users are predominantly using 2.x so when the tallies are in I will take a stab at a compat JAR for the version of Turbine that is most used and see what we can do to get it working in Summit. It may not be entirely pretty but I'm certain it can be done. > David Worms > > > On Friday, October 18, 2002, at 06:02 AM, Jason van Zyl wrote: > > > On Fri, 2002-10-18 at 08:02, [EMAIL PROTECTED] wrote: > >> All I know, is that as a new user, I would be very challenged to > >> figure out > >> what to use... > >> > >> Do I spend effort on 2.1, which is well tested, but at least two whole > >> releases behind the latest and greatest (4.x). > >> > >> Or, do I split the middle, and go with either 2.2 or 3.x, but then > >> why do > >> both of them have components of Fulcrum? And what is Fulcrum? > >> > >> If we have 4 seperate options, then I forsee many many emails goint > >> to the > >> users list on "What should I use to build my app...". > >> > >> Would it not be better to mash the rest of the good stuff in 2.2 into > >> 3.x, > >> and provide only 2.1, 3.0, and upcoming 4.0? Or, tell people to use > >> 2.2 > >> (not 2.1) and call 2.2 the well tested stable version. > >> > >> Having 4 options seems to much.... > > > > Definitely. As developers we have to consider this and try and unify to > > make things easier. I don't know what the ultimate solution is but 4 > > options definitely doesn't sound appealing. > > > >> Eric > >> > >> -----Original Message----- > >> From: Kasper Nielsen [mailto:news@;kav.dk] > >> Sent: Thursday, October 17, 2002 6:45 PM > >> To: Turbine Developers List > >> Subject: Re: Turbine community contributions > >> > >> > >> GREAT! > >> > >> > >> > >> Then we'll be able to present not only three but four choices to new > >> users: > >> > >> Turbine 2.1 Original and stable code base, well tested > >> > >> Turbine 2.2 Based on a decoupled Torque 3.0 (+ some of the fulcrum > >> services) > >> > >> Turbine 3.x Based on a decoupled Service layer Fulcrum + Torque 3.0 > >> > >> Turbine 4.x (codename summit) based on avalon > >> > >> > >> > >> ....... > >> > >> > >> > >> - Kasper > >> > >> > >>> I fully support the direction Jason is trying to push the > >>> design of applications and so do the other turbine developers, so > >>> there > >>> is no reason summit cannot be the basis for t4. But if there are > >>> others > >>> who have their livelihoods as tied up in t3 and fulcrum technology > >>> as I > >>> do, they will be very disheartened by statements that t3 and fulcrum > >>> should not be released and abandoned. They should be released and I > >>> will make sure that they are assuming I can overcome -1's on it. > >>> > >>> john mcnally > >> > >> > >> > >> -- > >> To unsubscribe, e-mail: > >> <mailto:turbine-dev-unsubscribe@;jakarta.apache.org> > >> For additional commands, e-mail: > >> <mailto:turbine-dev-help@;jakarta.apache.org> > > -- > > jvz. > > > > Jason van Zyl > > [EMAIL PROTECTED] > > http://tambora.zenplex.org > > > > In short, man creates for himself a new religion of a rational > > and technical order to justify his work and to be justified in it. > > > > -- Jacques Ellul, The Technological Society > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:turbine-dev-unsubscribe@;jakarta.apache.org> > > For additional commands, e-mail: > > <mailto:turbine-dev-help@;jakarta.apache.org> > > > > > -- > To unsubscribe, e-mail: <mailto:turbine-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:turbine-dev-help@;jakarta.apache.org> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: <mailto:turbine-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-dev-help@;jakarta.apache.org>
