Chris Kimpton wrote: >Hi, > >I am nearly there with this.... pending a few turbine patches to be >committed. > >Anyone got any concerns with this in general? > >--- Chris Kimpton <[EMAIL PROTECTED]> wrote: > >>Hi, >> >>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 >>have >>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 logger.
> >> >>Jetspeed points:: >> >>The DatabasePsmlManagerService uses Torque (in the import) - I >>tried >>to move it the late init, but that seems to never get called for >>that >>service... >> > >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:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
