> I was under the impression the logging facility would need to
> move to a
> service implementation to achieve this and that this task was
> underway.
You are right; otherwise, there is no ServletConfig object
to query the getRealPath() from...
> Is this what you are proposing or do you have a simpler
> implementation?
Not really. As I see it, moving the logging facility to a
service would have one drawback: it would not be possible
to use it from a stand-alone app that wants to use Turbine
as a class library, not a servlet (like torque does or will
do). Would this be a problem? I guess the logging facility
could be moved to a service and still present an interface
usable for these cases...
Anyway, this is my plan:
1. Implement a utility class to encapsulate the getRealPath()
thing as it is used today from several parts in the code.
This will go in util/ServletUtils.java. Change the rest
of Turbine to use this implementation.
2. What to do with the logging facility? I could make a simple
move to a service, leaving most of it as it is today,
hopefully keeping the ability to run from a stand-alone
app such as torque. How will this collide with the efforts
underway to move this to an Avalon- or IBM- based logging
service?
Opinions?
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
