You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Quinton McCombs <qm...@nequalsone.com> on 2003/04/24 19:24:15 UTC

Fulcrum (was: RE: village source)

> -----Original Message-----
> From: EPugh@upstate.com [mailto:EPugh@upstate.com] 
> Sent: Thursday, April 24, 2003 8:40 AM
> To: turbine-user@jakarta.apache.org
> Subject: RE: village source
> 
> 
> Okay, 
> I am starting to feel more and more lost on the whole fulcrum 
> thing..  It seems that fulcrum in jakarta-turbine-fulcrum CVS 
> has both the old Fulcrum based services, as well as my new 
> Avalon based HibernateService.  The HibernateService seems to 

Correct.

> work great in my app, by just including the fulcrum jar, and 
> using the this service: 
> services.AvalonComponentService.classname=org.apache.turbine.s
> ervices.avalon
> component.TurbineAvalonComponentService
> 
> However, that basically just means that I am using the 
> fulcrum jar as a repository, but not taking any advantage of 
> any of the fulcrum services, as they are to be deprecated, correct?

Correct.  When we are done, Fulcrum will not have any service manager
related code.  It will only be a repository of components.

> So the game plan going forward is to grab the various fulcrum 
> services that have been Avalonized that are in the plexus 
> cvs: 
> http://cvs.werken.com/viewcvs.cgi/fulcrum/?cvsroot=plexus and 
> move them over into the fulcrum cvs.  Since fulcrum was never 
> released, we can just ditch the fulcrum versions.  At least, 
> that is how I see it.

Pretty much....

> Eric Pugh
> 
> -----Original Message-----
> From: Henning P. Schmiedehausen [mailto:hps@intermeta.de]
> Sent: Thursday, April 24, 2003 4:04 AM
> To: turbine-user@jakarta.apache.org
> Subject: Re: village source
> 
> 
> EPugh@upstate.com writes:
> 
> >Leadro is working on a persistence interface/api so that if 
> you write 
> >your data objects, you can save them with OJB/Hibernate/Torque etc...
> 
> >I am currently banging my head through learning fulcrum.  I 
> just added 
> >a HibernateService to it, and need testers and comments!
> 
> >So, I think the wiki thing is a good idea....  If people can 
> test and 
> >help me get fulcrum properly integrated into t2.3 that would be even 
> >better!
> 
> Hm, "Learning Fulcrum" is basically "learning how to write a 
> Turbine Service". The only real differences are in the names 
> of the packages.
> 
> The code in org/apache/turbine/services/*.java and 
> org/apache/fulcrum/*.java was (is?) almost identical, Fulcrum 
> mainly uses much less classes because Jason cut much of the 
> bloated overhead out but the basic functionality was (at 
> least before the Avalonization; I didn't look at Fulcrum 
> after that) the same.
> 
> Using Fulcrum in Turbine-2.3 is (IMHO) not very reasonable. This is
> why: All the Fulcrum services are derived from Fulcrum base 
> classes. The Service Manager of Turbine, however, only knows 
> how to instantiate Services derived from Turbine base classes 
> _and_ the Service Broker of Turbine know only how to hand out 
> the Turbine derived services. So if you, e.g. use the 
> PoolService of Fulcrum, you can't get your Turbine code to 
> automagically use it, because the Service Broker will never 
> hand it out (only the Fulcrum one will) and using 
> TurbinePool.getService() will fail.
> 
> (That's how turbine-light was created. This is our internal 
> version where I removed everything from the turbine.jar that 
> is also in Fulcrum and replaced all references to this code 
> with fulcrum references. This works like a charm, but after 
> this brain transplantation, turbine-light is of course only 
> able to start Fulcrum services).
> 
> With Avalon (though I still think that some aspects of the 
> Lifecycle are overengineered but that's another story), we 
> will get common interfaces for Turbine Services and Fulcrum 
> Services and _then_ (in Turbine post-2.3) we will be able to 
> freely mix Fulcrum and Turbine services. And then we will 
> slay out everything that is duplicated in Fulcrum and Turbine 
> in terms of code.
> 
> ATM you can start Fulcrum with the ComponentService but it 
> doesn't help you much. You can't get a Fulcrum Service in 
> Turbine based code and a Turbine Service in Fulcrum code.
> 
> 	Regards
> 		Henning
> 
> -- 
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
> hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/
> 
> Java, perl, Solaris, Linux, xSP Consulting, Web Services 
> freelance consultant -- Jakarta Turbine Development  -- hero for hire
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org