4 Replies Latest reply on Apr 17, 2003 11:38 AM by juhalindfors

    j2ee.jar

    beaglebuddy
    beaglebuddy Apr 16, 2003 1:01 PM

      jboss 3.04 blows up as soon as I add sun's standard j2ee.jar file to the classpath. When I remove it, jboss starts up, but then I can't deploy any applications because (duh) all of the j2ee classes and interfaces aren't there.

      Anyone have any ideas?

      • 1986 Views
      • Tags:
        • 1. Re: j2ee.jar
          adrian.brock Apr 16, 2003 4:28 PM (in response to beaglebuddy)

          They are all there in server/default/lib/jboss-j2ee.jar

          DO NOT MODIFY THE CLASSPATH

          Regards,
          Adrian

            • Actions
          • 2. Re: j2ee.jar
            beaglebuddy
            beaglebuddy Apr 17, 2003 11:21 AM (in response to beaglebuddy)

            what do you mean do not modify the classpath?

            how am I supposed to provide access to all of my classes that are not packaged in ejbs?

              • Actions
            • 3. Re: j2ee.jar
              beaglebuddy
              beaglebuddy Apr 17, 2003 11:37 AM (in response to beaglebuddy)

              server/default/lib/jboss-j2ee.jar is 69k.
              sun's j2ee.jar is 8467k.

              obviously, jboss's j2ee.jar file is missing a huge number of classes.

              when you start the jboss server using the run.bat command, the classpath only includes the jdk 's tools.jar and jboss's run.jar. None of the jar files in the server/default/lib directory are included on the classpath.

                • Actions
              • 4. Re: j2ee.jar
                juhalindfors Apr 17, 2003 11:38 AM (in response to beaglebuddy)

                No, jboss-j2ee.jar is not missing huge number of classes. It contains all the interfaces you need to compile J2EE apps.

                HTH

                  • Actions