You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Henning Schmiedehausen (JIRA)" <ji...@apache.org> on 2006/11/20 22:02:02 UTC
[jira] Commented: (VELOCITY-500) Having to move Log and LogChute
objects around pollutes the C'tors
[ http://issues.apache.org/jira/browse/VELOCITY-500?page=comments#action_12451417 ]
Henning Schmiedehausen commented on VELOCITY-500:
-------------------------------------------------
Yeah, VELOCITY-500!
> Having to move Log and LogChute objects around pollutes the C'tors
> ------------------------------------------------------------------
>
> Key: VELOCITY-500
> URL: http://issues.apache.org/jira/browse/VELOCITY-500
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.5 beta1, 1.5 beta2
> Reporter: Henning Schmiedehausen
> Priority: Minor
>
> With most logging implementations like log4j or commons-logging, there is a factory class a method can request a Log object using
> Logger log = LogFactory.getLogger("some foo");
> and there is no need to drag a log object through C'tors into internal code just because one wants to log.debug() from deep inside Velocity. It would be nice if the LogChute code could also sprout some sort of Log Factory to allow this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org