I'd pick (3).

We're giving Glassfish a spin for now.  JBoss just had too many issues.

On 8/1/06, Gwyn Evans < [EMAIL PROTECTED]> wrote:
It's not /just/ Wicket - Googling for that error shows it in a number
of cases, but it looks to be down to "issues" with JBoss not coping
with log4j.jar in WAR files.

There look to be at least 3 options...
1) Configure JBoss to keep it's internal jars to itself (if you can)
2) Remove the log4j.war from any web apps you use
3) Try a different AppServer? :-)

Example URLs to check:


On 01/08/06, ksiow02 < [EMAIL PROTECTED]> wrote:
> Could someone help me with the following error? No sure why I've the logging
> error. The 4.0.4.GA Jboss server is running fine with other applications
> (i.e. Seam examples). Please help. Thanks.

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
Wicket-user mailing list

Reply via email to