You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Ben Peter <bp...@zentropypartners.com> on 2002/04/11 16:56:34 UTC

[TDK2.2-b1] using decoupled Fulcrum

Hi,

can someone clarify on the contents of TR.properties and Fulrum.properties in 
TDK2.2-b1? Which one is in use by default, or are both used?

In Fulcrum.properties, the new decoupled fulcrum classes are named, while in 
TR.properties the old classes are still referenced. I would like to switch to 
fulcrum's cvs HEAD, (because I want to use commons-fileupload's 
DefaultFileItem, which is the only FileItem with a write() mehtod that works 
for me) but am not quite clear on how I should proceed.

Can the duplicate entries in the two files be consolidated into one file? It's 
rather confusing to keep track of the two files, not knowing exactly what of 
them is used.

Also: if I do not change a thing, will tdk2.2-b1 use the decoupled torque 
3.0-b1 that is provided?

Cheers,
Ben


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: [TDK2.2-b1] using decoupled Fulcrum

Posted by Ben Peter <bp...@zentropypartners.com>.
Eric,

thanks a lot for your explanations which did help indeed.

I have tried to use the fulcrum upload, but as you said turbine is currently 
depending on it's own RunData service (there is none in fulcrum), so that I 
could not get it to use fulcrum's ParameterParser, let alone 
commons-fileupload's fileitem.

I have submitted a patch to the dev-list that brings new funtionality from 
commons-fileupload's FileItem to t2 - that was the easiest thing to do in that 
situation.

Perhaps someone involved in documentation could find a few puts to put a 
clearer statement of the status of decoupling. I think that I have read 
somewhere that "turbine 2.2 is using the decouple fulcrum and torque", which is 
rather  misleading.


Eric Dobbs wrote:
[ parts omitted ]

> As you probably know, Torque and Fulcrum are decoupled components which 
> used to be intertwined with the core parts of Turbine.  T2.2 still 
> contains the intertwined ancestors of Torque and Fulcrum and the 
> properties in TR.properties provide the configuration for them.  It 
> should be possible to use the decoupled services in Fulcrum by providing 
> the configuration details in Fulcrum.properties.  Your client code needs 
> to be importing the classes in org.apache.fulcrum in order for those 
> services to be active.

Ok, that is plain now. I hadn't imported any service code so far, as I was only 
using the tighly-integrated services (RunData, Upload) - which are propably too 
tighly integrated to drop them and use fulcrum.

> I don't think this has been widely tested at the moment.  I think most 
> projects using the decoupled Fulcrum are either using it separately from 
> Turbine, or are riding the bleeding edge with T3.

I was wondering. At least those that develop fulcrum must have some test 
environment to use the services in, and I would be surprised if that isn't 
turbine. Oh well, probably t3, yes.

> 
>> Also: if I do not change a thing, will tdk2.2-b1 use the decoupled 
>> torque 3.0-b1 that is provided?
> 
> 
> I don't think so, but I haven't looked as closely at this as I have 
> Fulcrum.
> 

Ok, I'll take a closer look myself once I'm comfortable with the t2/fulcrum 
relationship.


> Hope that helps.
Indeed.

Cheers,
Ben


-- 
Benjamin Peter                                          +49-69-96244395
Application Engineer                             Moerfelder Landstr. 55
(zentropy:partners)                            60598 Frankfurt, Germany


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: [TDK2.2-b1] using decoupled Fulcrum

Posted by Eric Dobbs <er...@dobbse.net>.
On Thursday, April 11, 2002, at 08:56  AM, Ben Peter wrote:

> can someone clarify on the contents of TR.properties and 
> Fulrum.properties in TDK2.2-b1? Which one is in use by default, or are 
> both used?

As you probably know, Torque and Fulcrum are decoupled components which 
used to be intertwined with the core parts of Turbine.  T2.2 still 
contains the intertwined ancestors of Torque and Fulcrum and the 
properties in TR.properties provide the configuration for them.  It 
should be possible to use the decoupled services in Fulcrum by providing 
the configuration details in Fulcrum.properties.  Your client code needs 
to be importing the classes in org.apache.fulcrum in order for those 
services to be active.

I don't think this has been widely tested at the moment.  I think most 
projects using the decoupled Fulcrum are either using it separately from 
Turbine, or are riding the bleeding edge with T3.

We have begun moving our application from T2.1 to T2.2.  We've chosen to 
continue using the older services until we have more time to test our 
application with the Fulcrum equivalents.  However, for the new 
functions in our app, we are using Fulcrum -- in particular the XMLRPC 
service.  This particular move took a little bit of elbow grease, but 
seems to be working fairly well.


> In Fulcrum.properties, the new decoupled fulcrum classes are named, 
> while in TR.properties the old classes are still referenced. I would 
> like to switch to fulcrum's cvs HEAD, (because I want to use 
> commons-fileupload's DefaultFileItem, which is the only FileItem with a 
> write() mehtod that works for me) but am not quite clear on how I 
> should proceed.

I haven't tried this with the upload stuff yet.  That particular example 
might be a bit nasty.  When last I looked at it, there was still some 
coupling between the old upload service and Turbine's ParameterParser.  
That's been a few weeks and some of these things have been changing 
quickly.  It may be easier now.


> Can the duplicate entries in the two files be consolidated into one 
> file? It's rather confusing to keep track of the two files, not knowing 
> exactly what of them is used.

You can control which set of services you are using in your import 
statements.

// to use the old service in your code
import org.apache.turbine.services.foo.FooService;

// to use the new service in your code
import org.apache.fulcrum.foo.FooService;

So looking at the import line will tell you which config file to pay 
attention to.  I'd suggest against consolidating the configurations for 
a while, 'cos the integration of T2.2 and the decoupled components is 
still pretty new.

> Also: if I do not change a thing, will tdk2.2-b1 use the decoupled 
> torque 3.0-b1 that is provided?

I don't think so, but I haven't looked as closely at this as I have 
Fulcrum.

Hope that helps.
-Eric


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>