Hello Hans, I am using Jboss 3.0.1
I have made an example of a servlet that communicates with an EJB run before. The problem that you might be having is that JBoss and Tomcat are two stand alone applications. Therefore, Tomcat is unable to see the context of the deployed applications on JBoss (I am just guessing here). In my opinion you hav two options. 1.) Don't use tomcat. After all it's just web application container. USE JETTY. Which is lighter and perhaps faster (dunno). Jetty is packaged with JBoss so deployment is just as easy. Also, you can see the context of your deployed EJBs from this embeded web container (Jetty). Be sure to place a web.xml in the WEB-INF directory, even if you don't put anything on the <web-app/> tag otherwise you won't be able to deploy your WAR in Jetty. with regards to any libraries that you might need, be sure to include them in the lib folder of JBoss. There are several "lib" folders, the one that has worked for me is: JBOSS_HOME\server\default\lib 2.) Use tomcat! So your preferred Web Application Container is Tomcat, you are used to it and you are happy with the way it performs, and you don't mind the space that it uses up on your hard drive (I am just being over synical). Then download one of the JBoss-Tomcat distributions. These are found in the same place where you found JBoss and you should be able to see the context of the deployed EJBs. I hope this helps. Tschuss, Ricardo ----- Original Message ----- From: "Hans Schmid" <[EMAIL PROTECTED]> To: "Jboss-User" <[EMAIL PROTECTED]> Sent: Wednesday, October 02, 2002 7:24 PM Subject: [JBoss-user] log4j 1.2x required by an external client? > 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 > ------------------------------------------------------- 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
