2 Replies Latest reply on Jan 17, 2003 9:53 AM by adrian.brock

    ClassNotFound in JBoss3.0.3_tomcat4.1.12

    bigb

      Hello,

      I deployed a .ear that contains my war file. It is working in
      JBoss-2-4.3_Tomcat-3.2.3 but not JBoss.3.0.3_tomcat-4.1.12. It started complaining about not able to find ActionFromBean (a deprecated api). I added it to the server/default/lib
      directory and that message disappeared. Then, however, it started complaining about not being able to find an action class. The welcome.jsp page displays fine. I am using Struts 1.0 and I use Ant1.5 to create the war and ear files.

      I believe the directory structure is correct (cause the application has been working in the previous version.

      Does this have to do with ClassLoader? How can I get around this?

      Any help is appreciated.

      Here is the trace:
      -----------------------------------------------------
      14:09:08,645 ERROR [Engine] action: No action instance for path /Index could be
      created
      14:09:08,645 ERROR [Engine] action: No action instance for path /Index could be
      created
      java.lang.ClassNotFoundException: com.mycompany.myapp.action.Index
      at org.jboss.mx.loading.UnifiedLoaderRepository2.loadClass(UnifiedLoader
      Repository2.java:166)
      at org.jboss.mx.loading.UnifiedClassLoader.loadClass(UnifiedClassLoader.
      java:283)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
      ...
      -----------------------------------------------------

        • 1. Re: ClassNotFound in JBoss3.0.3_tomcat4.1.12
          srmcatee

          I am having the same problem in Struts. My class exists in the WEB-INF/classes directory of the war.

          My jsp page has a form tag using a class declared by the type parameter. But JBoss is reporting the class is not found.

          Any one have any answers?

          • 2. Re: ClassNotFound in JBoss3.0.3_tomcat4.1.12

            With struts you have to put just about everything
            in WEB-INF/lib

            It uses Class.forName() which won't the
            application's classloader and so will fail to find
            classes in WEB-INF if you put struts/commons
            libs in server/default/lib

            There is a short statement about this shortcoming
            in the struts docs.

            Regards,
            Adrian