Rogelio, With the 2.3 release of Turbine we started pulling out the core services into the Fulcrum project. So things like Pool, XMLRPC, Intake etc can be used outside of Turbine. However, at this point, in 2.3 we have all the same services. However when 2.4 comes out they will be all deprecated, and Turbine will be using the Fulcrum equivalents. This will allow Turbine to be much stripped down. So, if you want to use a fulcrum compoenent then you add the config and role informaiton to the componentConfiguration.xml and roleConfiguration.xml.
If they are like Torque, where you need to load them when Turbine starts up (versus the first time you need them) then you do want to provide the line: services.AvalonComponentService.lookup =my.very.custom.fulcrum.Component To start it up. However, for most things, the first time you use it is soon enough. To see an example, look at the Adapters unit test for Fulcrum Security component. It demonstrates loading up a fulcrum component in Turbine. Additionally, it demonstrates using the adapters so that the Turbine thinks it is using it's own classes, but in reality is using the Fulcrum Security ones. Eric Pugh > -----Original Message----- > From: Robles, Rogelio [mailto:[EMAIL PROTECTED] > Sent: Monday, October 06, 2003 6:18 PM > To: 'Turbine Users List' > Subject: RE: Pool Service > > > Eric, > > Now that you're talking about the new fulcrum stuff, I have ambiguous > information about it, If I'm using Turbine-2.3 and I'd like > to use some > fulcrum components with it, what I need to do? Do I need to > add them to > TR.props or add them to the files componentConfiguration.xml and > roleConfiguration.xml, but then how do I tell Turbine to load them at > initialization time? > > List them like Torque? > services.AvalonComponentService.lookup = > org.apache.torque.avalon.Torque > > Do you have an example of what you need to do to add a component to a > Turbine environment? > > Thanks, > Rogelio > > > -----Original Message----- > > From: Eric Pugh [mailto:[EMAIL PROTECTED] > > Sent: Sunday, October 05, 2003 11:10 AM > > To: 'Turbine Users List' > > Subject: RE: Pool Service > > > > > > Javier.. > > > > Glad to see people are starting to pick up on the new fulcrum > > stuff! The > > Pool service is compatible with any Avalon container. While > > the home page > > has a little documentation, is is very rough. Any patch's to the > > documentation would be much appreciated! > > > > The best way to learn how to use the Pool service is to run > > the tests. From > > the /pool directory run 'maven test' to see the test case in > > action. Also, > > in CVS > > (http://cvs.apache.org/viewcvs/jakarta-turbine-fulcrum/pool/sr > c/test/) here > are the two role and config xml files used to configure the > pool service. > > Eric Pugh > > > -----Original Message----- > > From: Javier Ramos [mailto:[EMAIL PROTECTED] > > Sent: Friday, October 03, 2003 4:46 PM > > To: [EMAIL PROTECTED] > > Subject: Pool Service > > > > > > Hallo, > > > > I am interested in the Pool service concept and would > like to use > > this and other fulcrum services in my new developments. > However, I am > > finding it difficult to figure aout how to do it. The documentation > > seems a bit scarce. > > > > I downloaded maven and build the jar file for > fulcrum-1.0-alpha-3, > > but now I do not know how to continue. > > > > Is it enough to put this jar in my build & runtime classpaths to > > start using the classes? Are there javacoc's for them? Do I need to > > initialise fulcrum by providing some properties or xml file? In the > > documents I read about the 'role' configuration, but I cannot find > > anywhere what this 'role' thing is about. > > > > I find the ideas inside the turbine projects very > > interesting and am > > willing to test them for a new project that will be starting > > very soon. > > Any help will be much appreciated... > > > > Javier Ramos > > > > > --------------------------------------------------------------------- > 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]
