LogView4j Log4J Event Viewer

Hi aberezin,

I'm surprised that you had to add logview4j-1.0.3.jar to your server classpath.

What was the stack trace you got from JBoss? i.e. what class was it looking for?

Perhaps you included a reference to one of the Logview4J classes in error in your code, thus the dependancy, or referenced a Logview4J class in one of your log4j.xml or log4j.properties files?

I also use JBoss and was fairly careful to make sure that the JBoss server only required the socket appender that comes with Log4J by default.

In some cases, you might need to add the Log4J jar itself to the JBoss classpath, but probably not logview4j-1.0.3.jar

At all times, Logview4J should be separated from the source logger via a socket, thus no class dependancies at run time?

I stand to be corrected though =]

Any general feedback on usability features etc is appreciated,

Josh