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
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
The other two services are/were parts of the integrated Torque support
and its functions might be supported by the decoupled Torque but I'm not
too sure about this. Martin? Quinton?
>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.
>Do i need to implement Fulcrum? Is the fact that I dont use Fulcrum the
>reason why none of this seems to make sense to me?
No. Fulcrum support is currently only by being able to start Fulcrum
services via the (Avalon)ComponentService. The services integrated in
Turbine should contain all bug fixes from Fulcrum but I'm not sure about
the other way round.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
