Re: Wicket + jboss 4.0.5 + slf4j-log4j12 markup refresh problem issue
Hi Lukasz, I use about the same configuration as yours. I think you can safely replace the provided version of log4j (in the lib directory) with a more recent one. I have a production environment working with log4j 1.2.8, other test environments I use have more recent versions. My production environment is producing a huge amount of logging and no issues there with logging. Bernard. Lukasz Kucharski a écrit : Hi group Did anyone use wicket witch such configuration - i know this may sound silly but I'm having serious issues with slf4j binding for log4j. Jboss internally uses very old implementation of log4j for which i guess no slf4j binding exists (pre 1.2.x versions i guess). I run wicket application successfully and log4j logging is working but my wicket markup does not refresh, ever! This is because when refreshing worker thread is starting it generates this error: 2008-09-11 15:46:04,781 ERROR [] thread.Task - Task ModificationWatcher terminated java.lang.NoSuchMethodError: org.apache.log4j.Logger.isTraceEnabled()Z at org.slf4j.impl.Log4jLoggerAdapter.isTraceEnabled(Log4jLoggerAdapter.java:81) at org.apache.wicket.util.thread.Task$1.run(Task.java:107) at java.lang.Thread.run(Thread.java:619) which makes it unusable - my markup does not get refreshed. This is serious concern for us. Please help. Regards Lukasz - 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]
Wicket + jboss 4.0.5 + slf4j-log4j12 markup refresh problem issue
Hi group Did anyone use wicket witch such configuration - i know this may sound silly but I'm having serious issues with slf4j binding for log4j. Jboss internally uses very old implementation of log4j for which i guess no slf4j binding exists (pre 1.2.x versions i guess). I run wicket application successfully and log4j logging is working but my wicket markup does not refresh, ever! This is because when refreshing worker thread is starting it generates this error: 2008-09-11 15:46:04,781 ERROR [] thread.Task - Task ModificationWatcher terminated java.lang.NoSuchMethodError: org.apache.log4j.Logger.isTraceEnabled()Z at org.slf4j.impl.Log4jLoggerAdapter.isTraceEnabled(Log4jLoggerAdapter.java:81) at org.apache.wicket.util.thread.Task$1.run(Task.java:107) at java.lang.Thread.run(Thread.java:619) which makes it unusable - my markup does not get refreshed. This is serious concern for us. Please help. Regards Lukasz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket + jboss 4.0.5 + slf4j-log4j12 markup refresh problem issue
Have you looked at this: http://wiki.jboss.org/wiki/ClassLoadingConfiguration There's a section in there about how to isolate your application from JBoss' stuff. On Thu, Sep 11, 2008 at 12:55 PM, Lukasz Kucharski [EMAIL PROTECTED] wrote: Hi group Did anyone use wicket witch such configuration - i know this may sound silly but I'm having serious issues with slf4j binding for log4j. Jboss internally uses very old implementation of log4j for which i guess no slf4j binding exists (pre 1.2.x versions i guess). I run wicket application successfully and log4j logging is working but my wicket markup does not refresh, ever! This is because when refreshing worker thread is starting it generates this error: 2008-09-11 15:46:04,781 ERROR [] thread.Task - Task ModificationWatcher terminated java.lang.NoSuchMethodError: org.apache.log4j.Logger.isTraceEnabled()Z at org.slf4j.impl.Log4jLoggerAdapter.isTraceEnabled(Log4jLoggerAdapter.java:81) at org.apache.wicket.util.thread.Task$1.run(Task.java:107) at java.lang.Thread.run(Thread.java:619) which makes it unusable - my markup does not get refreshed. This is serious concern for us. Please help. Regards Lukasz - 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]
Re: Wicket + jboss 4.0.5 + slf4j-log4j12 markup refresh problem issue
Have you looked at this: http://wiki.jboss.org/wiki/ClassLoadingConfiguration There's a section in there about how to isolate your application from JBoss' stuff. Thanks for the link. I'll try those solutions tomorrow when I get back to work. I guess this is similar to what we used to do with WLS 8.1 and its prefer-webinf-classes configuration tag in web.xml. I must say I've always been bit sceptic about messing with standard class loading order in app servers and containers. I must say, I'm surprised Wicket will not work out of the box in such a popular environment. I did not expect to encounter such problems during evaluation stage. -- Pozdrawiam Lukasz Kucharski [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket + jboss 4.0.5 + slf4j-log4j12 markup refresh problem issue
If you're just evaluating, try creating a quickstart (http://wicket.apache.org/quickstart.html) and just use the embedded Jetty server (mvn jetty:run or run the Start class in your project) to check things out. It works quite well. On Thu, Sep 11, 2008 at 2:22 PM, Lukasz Kucharski [EMAIL PROTECTED] wrote: Have you looked at this: http://wiki.jboss.org/wiki/ClassLoadingConfiguration There's a section in there about how to isolate your application from JBoss' stuff. Thanks for the link. I'll try those solutions tomorrow when I get back to work. I guess this is similar to what we used to do with WLS 8.1 and its prefer-webinf-classes configuration tag in web.xml. I must say I've always been bit sceptic about messing with standard class loading order in app servers and containers. I must say, I'm surprised Wicket will not work out of the box in such a popular environment. I did not expect to encounter such problems during evaluation stage. -- Pozdrawiam Lukasz Kucharski [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]
Re: Wicket + jboss 4.0.5 + slf4j-log4j12 markup refresh problem issue
By the way, I wouldn't fault Wicket too much when it comes to the JBoss/Log4j issue. Many others have had problems and it has nothing to do with Wicket itself. http://www.theserverside.com/discussions/thread.tss?thread_id=29870 http://www.theserverside.com/discussions/thread.tss?thread_id=34146 http://www.techienuggets.com/Detail?tx=22 http://raibledesigns.com/rd/entry/fun_with_log4j_and_jboss On Thu, Sep 11, 2008 at 7:13 PM, James Carman [EMAIL PROTECTED] wrote: If you're just evaluating, try creating a quickstart (http://wicket.apache.org/quickstart.html) and just use the embedded Jetty server (mvn jetty:run or run the Start class in your project) to check things out. It works quite well. On Thu, Sep 11, 2008 at 2:22 PM, Lukasz Kucharski [EMAIL PROTECTED] wrote: Have you looked at this: http://wiki.jboss.org/wiki/ClassLoadingConfiguration There's a section in there about how to isolate your application from JBoss' stuff. Thanks for the link. I'll try those solutions tomorrow when I get back to work. I guess this is similar to what we used to do with WLS 8.1 and its prefer-webinf-classes configuration tag in web.xml. I must say I've always been bit sceptic about messing with standard class loading order in app servers and containers. I must say, I'm surprised Wicket will not work out of the box in such a popular environment. I did not expect to encounter such problems during evaluation stage. -- Pozdrawiam Lukasz Kucharski [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]
Re: Wicket + jboss 4.0.5 + slf4j-log4j12 markup refresh problem issue
On Thu, Sep 11, 2008 at 11:22 AM, Lukasz Kucharski [EMAIL PROTECTED] wrote: I must say, I'm surprised Wicket will not work out of the box in such a popular environment. I did not expect to encounter such problems during evaluation stage. why does such a popular environment force outdated dependencies onto its users? -igor -- Pozdrawiam Lukasz Kucharski [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]
Re: Wicket + jboss 4.0.5 + slf4j-log4j12 markup refresh problem issue
Lukasz, I agree that this is an irritating constraint JBoss, and others, inadvertently force on their users and it's a shame to lose time fiddling around with this stuff - but if that's your stack, then I guess you need a workaround, eg try Wicket 1.2.x (not what I would recommend). Have you asked the JBoss community if they have any solutions to this reliance on legacy libraries and inevitable conflicts? I would be surprised if you were the first to come across this type of issue as many JBoss users develop/deploy using the up to date versions of other components of their preferred stacks. Also note that http://java.dzone.com/articles/whats-new-seam-21-an-interview Seam 2.1 has full support for Wicket (as a civilised option for the view layer), so they may have solved this problem for you already. Regards - Cemal http://www.jWeekend.co.uk http://jWeekend.co.uk Lukasz Kucharski wrote: Have you looked at this: http://wiki.jboss.org/wiki/ClassLoadingConfiguration There's a section in there about how to isolate your application from JBoss' stuff. Thanks for the link. I'll try those solutions tomorrow when I get back to work. I guess this is similar to what we used to do with WLS 8.1 and its prefer-webinf-classes configuration tag in web.xml. I must say I've always been bit sceptic about messing with standard class loading order in app servers and containers. I must say, I'm surprised Wicket will not work out of the box in such a popular environment. I did not expect to encounter such problems during evaluation stage. -- Pozdrawiam Lukasz Kucharski [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Wicket-%2B-jboss-4.0.5-%2B-slf4j-log4j12-markup-refresh-problem-issue-tp19439480p19448042.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
