Sorry, you're right, it's not removed.
I said it was removed, because I used it and I take a compilation error, and 
eclipse no more find them.
I don't understand.
Sorry about the noice.

/david

Matej Knopp wrote:
Removed? They added it in 1.4.

-Matej

On 9/5/07, David Bernard <[EMAIL PROTECTED]> wrote:
Hi,

The 'trace' log level is removed from the last version of slf4j.
In my project, I replaced trace(...) and is isTraceEnabled() by debug(...) and 
isDebugEnabled().
I also use logback :
* "successor" of log4j
* slf4j native interface
* allow configuration from xml
* allow test and run configuration

I run the webapp with maven "mvn jetty:run" and change into eclipse (under 
src/main/java for .java and .html) => reload/restart (after 60s).

I'm not a wicket developper, only a user but I expect it could help you.

/david

Tauren Mills wrote:
This might just be my ignorance, but it seems there are some issues
with SLF4J 1.4 used in Wicket, or at least wicket-phonebook.  I want
to find out what combination of logging jars should be used.

I have a project that I based on wicket-phonebook.  I'm using wicket
from trunk.  I have updated some of the jars and now have the
following in my build path:
nlog4j-1.2.25.jar
slf4j-api-1.4.2.jar
slf4j-log4j12-1.4.2.jar

After a recent wicket trunk update, I started getting errors in:
org.apache.wicket.util.thread.Task.run()

When I start my application and hit the home page, the
ModificationWatcher Task has an exception at line 103:

if (log.isTraceEnabled())

It appears that nlog4j-1.2.25 doesn't have the method
Logger.isTraceEnabled().  I tried to use a current log4j that does
have it, but got tons of exceptions when I ran the app in Jetty.  The
nlog4j site says that new developments are in the Logback project:
http://logback.qos.ch/download.html

I am not familiar with Logback.  Do others use it with slf4j?  What is
the recommended combination of jars when using the latest wicket from
trunk?  What are the wicket developers using?

Also, it seems that any changes I make to HTML files are not
automatically reloaded while the app is running in Eclipse.  I have to
restart the app to see the html changes. I'm assuming that is related
to this issue.

Thanks!
Tauren

---------------------------------------------------------------------
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