On Tue, 2003-03-18 at 17:59, Henning P. Schmiedehausen wrote: > Bill <[EMAIL PROTECTED]> writes: > > >So where did the features these services provided go?... > > Logging got replaced with integrated Log4j support in the Turbine core. > We now load a Log4j config file at startup and provide Log4j support. > The o.a.t.util.Log class is kept but deprecated for the 2.3 release and > will provide code compatibility. It will go post-2.3
Thanks I eventually turned up the doc I needed. > Resources got replaced by using commons-configuration everywhere in the > code. The o.a.t.services.TurbineResources facade is kept for the 2.3 > release and will go post-2.3 Configuration is in the Sandbox, and according to the Commons site, code in the Sandbox is 'use at your own risk.' Are we reasonably sure that this code is at a stable point? I'm a little concerned in that I dont want to spend the time getting comfortable with this, if isnt going to stick around. > >I've only found two references to these changes in the all the docs > >(including Eric's wiki entry), and none of these references explain the > >change. > > It definitely in the post-2.2 changes.xml file. No it isnt. All that is in that file is a statement of the change, it makes no indication of how/what replaced the services. This is the entry from the changes page for TurbineResources: # removed the TurbineResources Service. So what was the final decision about the Fulcrum services. Jason mentioned finishing some porting to Avalon components, but I got the impression that Henning saw a problem with that. I just need to know what I am in store for here? Is 'avalonization' where we are going? And finally thank you (Quinton, Jason, and Henning) for your patience and help. I fell behind in keeping up with the changes to the framework and catching up was more daunting than expected. Thanks again -b --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
