Robert Burrell Donkin ha scritto:
On Mon, May 12, 2008 at 2:54 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Robert Burrell Donkin ha scritto:
On Mon, May 12, 2008 at 10:04 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
What are the advantages of this class over the direct use of
commons.logging LogFactory ?
it allows the shared log instance can be set
I'm not a commons-logging expert, but can't this be already done by using
commons-logging specific implementation configurations even if each class
directly calls the LogFactory.getLog() method?
that's not easy to do programmatically: this way is not how i would
have done it but is not unreasonable.
ok, let's delay this until the IoC change is there.
all the singletons should really be replaced by IoC but that would
require some effort and entail some risk
+1
Should we add a JIRA issue for the next releases, so we are better aware of
this?
should be an existing IoC task: just include it as a subtask
There is https://issues.apache.org/jira/browse/JSIEVE-16 but it is
marked as resolved so I didn't find it in my searches.
Can we simply reopen it and remove the "affect version 0.2" so it will
not show up in 0.2 changelog/openissues but we will have it in the roadmap?
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
