portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Santiago Gala <sg...@hisitech.com>
Subject Re: Using current Torque with Jetspeed - a few problems...
Date Tue, 02 Apr 2002 21:54:27 GMT
Chris Kimpton wrote:

>I am nearly there with this.... pending a few turbine patches to be
>Anyone got any concerns with this in general?
>--- Chris Kimpton <kimptoc_mail@yahoo.com> wrote:
>>Turbine points::
>>I have had to add a log4j.properties file covering the stratum,
>>torque and fulcrum appenders - this doesn't sound right - but maybe
>>this is the first time several disparate log4j-using components
>>been used together?
>Since torque and some of the other new components use log4j, it seems
>the cleanest way forward is to default to using log4j file logging
>for jetspeed.
>Is that ok with everyone?
I thought we were already using it, but as we are using Turbine logging 
service I could be wrong. At least you could configure log4j as default 

>>Jetspeed points::
>>The DatabasePsmlManagerService uses Torque (in the import) - I
>>to move it the late init, but that seems to never get called for
>I got this working - so the dbpsml import is now done in the late
>init (due to its reliance on Torque which is loaded between early and
>late inits).
>Any concerns with this?  Obviously its an impact on the first user -
>but then again, it should probably be turned off once the first
>import is done anyway...
I have global concerns with service initialization in turbine2, but none 
specially with this.

To unsubscribe, e-mail:   <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-dev-help@jakarta.apache.org>

View raw message