5 Replies Latest reply on Jul 30, 2004 5:50 PM by cdmojoli

    javax.servlet compile error

      I'm trying to build nukes from the current (7/30/04) snapshot and receive the following error. Apperently I need to place servlet.jar somewhere in the directory tree. If this is true - how and where?

      Any help would be appreciated.

      Scott


      _default:compile-classes:
      [depend] Deleted 0 out of date files in 0 seconds
      [javac] Compiling 201 source files to C:\Work\nukes\nukes\output\classes
      [execmodules] C:\Work\nukes\nukes\src\main\org\jboss\nukes\html\Page.java:11: package javax.servlet does not exist
      [execmodules] import javax.servlet.RequestDispatcher;
      [execmodules] ^

        • 1. Re: javax.servlet compile error

          Usually javax.servlet.RequestDispatcher is contained in several jars in the JBOSS_HOME area.
          ./server/all/lib/javax.servlet.jar for example.
          Against which version of JBOSS are you compiling?
          Are you calling ant directly or through the bat/sh scripts?

          • 2. Re: javax.servlet compile error

            I'm compiling against JBoss version 3.2.5 and am using the build.bat file in the nukes/build directory.

            Scott

            • 3. Re: javax.servlet compile error

              I see.

              The problem with Nukes and 3.2.5 is, that in 3.2.5 some libs were rearranged. I would suggest to stick with 3.2.3. Works fine for me. Just give the bunch some time to catch up with the server release :-)

              • 4. Re: javax.servlet compile error

                Version 3.2.3 worked fine. Thanks!

                Scott

                • 5. Re: javax.servlet compile error

                  Actually, there's more to 3.2.5 than just rearranged jars. At least a couple of classes were moved and methods changed.

                  org.jboss.mx.interceptor.Invocation is now import org.jboss.mx.server.Invocation

                  org.jboss.mx.interceptor.InvocationException is now import org.jboss.mx.server.InvocationException

                  This affects solely LifeCycleInterceptor.java, so I just trivially changed the imports. The symbols were recognized but some methods weren't available as expected by the code so I didn't get it to work.