By the way (not to start a flame war or anything), but "clogging" has
been working just fine for us.  We use it along with SLF4J using the
adapter,  We've had no problems at all.  Don't get me wrong, I am
aware of the issues with Commons Logging and I've argued for us to
change the way it works to be more slf4j-like.  I suggested it a LONG
time ago...

http://www.opensubscriber.com/message/[email protected]/8725291.html



On Thu, Nov 19, 2009 at 12:09 AM, Igor Vaynberg <[email protected]> wrote:
> i wouldnt, commons logging, aka clogging, has been a bane of web
> applications for a long time...
>
> wicket uses slf4j, why dont you do the same? still declaring your
> loggers static.
>
> -igor
>
> On Wed, Nov 18, 2009 at 9:07 PM, Lester Chua <[email protected]> wrote:
>> I think I'll use this then. I was reluctant to because of the need to
>> introduce yet another library (some examples used this).
>>
>> Thanks!
>>
>> Lester
>>
>> James Carman wrote:
>>>
>>> Commons Logging?
>>>
>>> On Wed, Nov 18, 2009 at 11:11 PM, Lester Chua <[email protected]>
>>> wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> I'm using log4j as my logging tool.
>>>> But when I add log4j loggers into my components, I get serialization
>>>> issues.
>>>> Wicket gives serialization errors because of the logger.
>>>>
>>>> E.g.
>>>>
>>>> class SomeForm extends Form {
>>>>
>>>>  Logger logger = LogManager.getLogger(SomeForm.class);
>>>>
>>>>  public void someMethod() {
>>>>     logger.debug("Some Message");
>>>>  }
>>>>
>>>> }
>>>>
>>>> This class will give an serialization error. Wicket complains about
>>>> serializing logger.
>>>> Is there a recommended way to do logging in wicket to avoid this?
>>>>
>>>> Thanks in advance.
>>>>
>>>> Lester
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to