In fact, I think someone on IRC had that issue today. He said:
"michaelb joined the chat room.
[3:01pm]michaelb:hi
[3:02pm]michaelb:the logging of the gui demo doesn't seem to work out of the
box"
Unfortunately he was gone by the time I replied to him.
I'm fairly confident the issue is to do with this. log4j.xml modifications when using
the GUI have no effect without it.
I had this issue myself when trying to enable logging to figure out what was wrong with
Hot Rod. That's how I realised that log4j jar was not on the classpath.
On Jul 1, 2010, at 5:11 PM, Manik Surtani wrote:
Hmm ... has this been a problem for people so far?
On 1 Jul 2010, at 16:05, Galder Zamarreño wrote:
> At least Infinispan -all.zip distro does not include a log4j jar in the root lib/
directory.
>
> This means that by default it logs using JDK logging. However, we ship an
etc/log4j.xml and it might not be obvious to people that they need to bring in log4j.jar
to see changes being made to etc/log4j.xml having an effect.
>
> So, I'd propose to include a log4j jar in the root lib/ directory.
>
> Any objections to that?
> --
> Galder Zamarreño
> Sr. Software Engineer
> Infinispan, JBoss Cache
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache