Hi All.

There seems to be a lot of confusion about TDK 2.2b1, Fulcrum, and 
Torque.  I thought I'd offer what I know to hopefully clear things up.

Right now the TDK 2.2b1 includes Fulcrum and Torque.  They happily 
co-exist.  That does not mean they are actually working together.  For 
example, the settings for services in Fulcrum.properties do not in any 
way override the similar settings in TurbineResources.properties.  Keep 
in mind that the TDK is beta.  And it's beta 1.  Some assembly 
required.  And Fulcrum and Torque have not been released yet.  Some 
assembly required.  If you're going to go down this road today, then you 
will have some work to do.

If you're just getting acquainted with Turbine, stick with TDK 2.1 for a 
while.  Progress on TDK2.2 has slowed lately.  I suspect that's 'cos the 
Scarab developers are trying to get Scarab released, and a number of the 
other turbine developers are trying to get Maven released.  So progress 
on the TDK has slowed.  Please be patient, or lend a hand.


For those of you who still want to play with TDK2.2b1, here's what I can 
tell you.  I've been updating our Turbine 2.1 app to use 2.2b1.  I 
started some documentation about the process, but didn't keep up with 
it.  I'll include what I know so far.

1. I added and replaced jars in lib directory:
    turbine-2.2-b1.jar
    stratum-1.0-b1.jar
    fulcrum-3.0-b1.jar
    torque-3.0-b1.jar
    commons-lang-0.1-dev.jar

I found no other jars that needed adding or replacing for our 
application.  Your miliage may vary.  It might be worth replacing all of 
turbine's dependancies.  I chose to find the minimum I could get away 
with.  (I should note that I'm not sure what else I might have had to 
add since I wrote that list.  There may be other requirements.)

2. I carefully updated TurbineResources.properties

For this purpose I used emacs and ediff to compare our TR.p with the one 
in the Turbine 2 repository.  ediff made this process much more easy 
than it might otherwise have been.  For the emacs impared I would 
recommend (ahem, learn emacs 8^) using diff -u to compare the changes.  
There are quite a few things that are different and diff -u might help 
you focus your attention on the differences.

At this point I was able to successfully conduct a few tests and explore 
around our application.  Everything seemed to work as before.  But our 
app was NOT using anything from Torque nor Fulcrum.  It was just working 
side-by-side with them.


That much was good news.  All I had to do was drop in the b1 jars and 
update the properties file and our application worked as before.  I'll 
say this again 'cos it bears repeating:  at that point, our application 
was NOT using anything from the decoupled Torque nor Fulcrum.  The 
non-decoupled ancestors for Torque and Fulcrum are still in the Turbine 
.jar in accordance with Turbine's deprecation policy.  This gives us a 
platform from which we can migrate to using Torque and Fulcrum at our 
own pace (which will be slow).

Introducing stuff from Fulcrum has not been completely smooth, however.  
In our specific case, the reason for moving to 2.2 is so that we could 
take advantage of Fulcrum's XMLRPC service.  But I had to fix some 
things in Fulcrum in order to make it work with Turbine correctly.  That 
fix should apply rather broadly to other Fulcrum services which will 
help others to do something similar.  But it also means you need to use 
one of the nightly builds, or build fulcrum yourself.  (for the nightly 
builds http://jakarta.apache.org/builds/jakarta-turbine/nightly/)

At the moment we're getting along fine with the b1s for torque and 
stratum, but building our own turbine2 and fulcrum jars from cvs HEAD.  
(If you don't want to roll your own, you could get away with nightly 
builds for those jars.)

I can't say anything about getting Turbine 2 working with decoupled 
Torque, because I haven't tried it myself.  But Brian Lawler's posting 
yesterday outlines some problems pretty clearly:
http://nagoya.apache.org:8080/eyebrowse/ReadMsg?listName=turbine-
[EMAIL PROTECTED]&msgNo=3448

If you're just getting started, use TDK2.1.  Wait until some others have 
blazed the trail a little.  If you want to dig into the 2.2 stuff, 
patches are probably necessary and always welcome!  And we'll thank you 
for the help blazing these trails.

Hope that helps.
-Eric

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to