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]
