Eddy Young wrote:
Hi all,
Is there a known classloader-related error between RIFE and Log4J?
Indeed, there was a classloader-related problem between RIFE and Log4j,
as Geert managed to track down. But, it is debatable whether the fault
can be attributed to RIFE at all. If you want to know the specifics,
please ask. We can then post a detailed analysis which might even be
useful to troubleshoot similar problems in your applications.
In short, the solution is to move Log4J jar-files from WEB-INF/lib into
common/lib of the servlet container *and* restart the container.
Eddy
--
http://coding.mu
http://priscimon.com/blog
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
