Hi, I just updated from Jboss 3.0.2 to 3.0.3. when my Webapp client (using log4j-1.1.3) creates the InitialContext to connect to JBoss, it fails with
2002-10-02 14:43:10,226 451040 [Thread-21] DEBUG (services.ejb.EJBService) - JNDI test connection failed java.lang.NoClassDefFoundError: org/apache/log4j/Level This class is present in log4j_1.2x and up only! We use Jboss for handling EJB's only. Our System runs on a standalone Tomcat 3.3.1. The servlets (actually helper classes) connect via the standard JNDI lookup mechanism to JBoss. Any Ideas, why the use of jbossall-client.jar by our Webapp forces this Webapp to use Log4J at all, and especially a special version of it? It is not a big deal for us, because we have to update to log4j-1.26 anyway. It is just strange from an architectural point of view. (and please do not add log4j into the jbossall-client.jar. It is already overloader IHMO) I stopped trying to find out, which of the many client jar files are actually required to execute simple Session beans. Thanks for a great product, Hans Schmid einsurance Agency AG Information Technology Bayerstra�e 33 80335 M�nchen Tel: +49-89-55292- 860 Fax: +49-89-55292- 855 eMail: [EMAIL PROTECTED] http://www.einsurance.de ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
