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.
Is this what you are proposing or do you have a simpler implementation?
John McNally
"Diethelm Guallar, Gonzalo" wrote:
>
> I noticed that the location of a logfile cannot be specified
> relative to the context root directory, since it is not using
> the getRealPath() trick. I also noticed this trick is used in
> several places with code that is identical everywhere.
>
> * Would it be Ok to implement the getRealPath() thing in a
> public method, and use it from everywhere it is being used
> now (mainly the template services)? If yes, what would be
> the right Turbine class to put this?
>
> * Would it be Ok to change the handling of TR.props so that,
> at least, the logfile location can be specified relative to
> the context root directory?
>
> If the answer to these questions is yes, I will make this change.
> Thanks,
>
> --
> 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]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
