9 Replies Latest reply on Feb 5, 2004 10:59 AM by tbauer

    JSP compilation error using regular javac in JB3.2.3

    tbauer

       

      "tbauer" wrote:
      Using regular web.xml setting (no JIKES) and still getting bogus JSP compilation errors...compile claims method doesn't exist which is totally untrue....

      13:14:33,039 ERROR [STDERR] An error has happened:
      13:14:33,040 ERROR [STDERR] org.apache.jasper.JasperException: Unable to compile class for JSP

      An error occurred at line: 0 in the jsp file: /jsp/modifyFacilityForm.jsp

      Generated servlet error:
      [javac] Compiling 1 source file
      [javac] /Applications/jboss-3.2.3/server/default/work/MainEngine/localhost/_/jsp/modifyFacilityForm_jsp.java:891: cannot resolve symbol
      [javac] symbol : method getTaxPayerId ()
      [javac] location: class com.icshealth.model.FacilityModel
      [javac] out.print(FacilityModel.getTaxPayerId());
      [javac] ^



      An error occurred at line: 0 in the jsp file: /jsp/modifyFacilityForm.jsp

      Generated servlet error:
      [javac] /Applications/jboss-3.2.3/server/default/work/MainEngine/localhost/_/jsp/modifyFacilityForm_jsp.java:937: cannot resolve symbol
      [javac] symbol : method getTaxPayerId ()
      [javac] location: class com.icshealth.model.FacilityModel
      [javac] out.print(FacilityModel.getTaxPayerId());
      [javac] ^



      An error occurred at line: -1 in the jsp file: null

      Generated servlet error:
      [javac] /Applications/jboss-3.2.3/server/default/work/MainEngine/localhost/_/jsp/modifyFacilityForm_jsp.java:1121: cannot resolve symbol
      [javac] symbol : method getTaxPayerId ()
      [javac] location: class com.icshealth.model.FacilityModel
      [javac] out.print(FacilityModel.getTaxPayerId());
      [javac] ^
      [javac] 3 errors
      13:14:33,044 ERROR [STDERR] at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130)
      13:14:33,044 ERROR [STDERR] at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293)
      13:14:33,044 ERROR [STDERR] at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353)
      13:14:33,044 ERROR [STDERR] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
      13:14:33,045 ERROR [STDERR] at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473)
      13:14:33,045 ERROR [STDERR] at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190)
      13:14:33,045 ERROR [STDERR] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
      13:14:33,045 ERROR [STDERR] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
      13:14:33,045 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
      13:14:33,046 ERROR [STDERR] at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
      13:14:33,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432)
      13:14:33,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356)


        • 1. Re: JSP compilation error using regular javac in JB3.2.3
          darranl

           

          "darranl" wrote:
          "darranl" wrote:
          Is your JAVA_HOME environment variable set correctly?


          • 2. Re: JSP compilation error using regular javac in JB3.2.3
            tbauer

             

            "tbauer" wrote:
            Uhh, yes... JAVA_HOME=/Library/Java/Home
            It's always been that way...If I undeploy the application and redeploy it the bogus errors usually go away..

            I have tried with BOTH the regular and JIKES compiler and I get this error intermittenly...It does not happen on 3.2.1...

            I really wish the JBoss group would settle on something and stick to it. Changing to Tomcat because you hired the developer (or is it a better web container) should not break existing generic code.

            And no, I'm not going to pay $200/hr for development support for something that should work as advertised out of the box.


            • 3. Re: JSP compilation error using regular javac in JB3.2.3
              darranl

               

              "darranl" wrote:
              Doesn't happen on 3.2.1 with Tomcat or Jetty?

              What happens with JBoss 3.2.3 with Jetty?


              • 4. Re: JSP compilation error using regular javac in JB3.2.3
                rtucker

                I've got the same problem.

                [javac] Compiling 1 source file
                [javac] C:\jboss-3.2.3\server\default\work\MainEngine\localhost\AgencyManagementWeb\jsp\detail_search_jsp.java:220: cannot resolve symbol
                [javac] symbol : method getCountrySelectList ()
                [javac] location: class com.tclick.agencyManagement.search.SearchParams
                [javac] out.print(sp.getCountrySelectList());

                The odd this is all I have to is change the name of the class "SearchParams" to "SearchParam" and the jsp will compile.

                What's going on here?

                • 5. Re: JSP compilation error using regular javac in JB3.2.3
                  tbauer

                  I have two different installations of JBoss on my development system, and to switch from one to the other, I only have to change my JBOSS_HOME env variable.

                  I am (and have been) using JBoss 3.2.1 with Jetty for MONTHS to a year, and have NEVER had this problem. Whenever I use 3.2.3 with Tomcat, I start getting these errors, whether my web.xml is configured to use JIKES or regular javac to do jsp compiles. Its as if somehow the whole xxx_jsp.java file IS TRUNCATED somehow before the compiler gets done with it....

                  Here's my application startup echo:

                  JBoss Bootstrap Environment

                  JBOSS_HOME: /Applications/jboss-3.2.3

                  JAVA: /Library/Java/Home/bin/java

                  JAVA_OPTS: -Dprogram.name=run.sh -Xms384m -Xmx640m

                  CATALINA_OPTS: -Dbuild.compiler.emacs=true

                  CLASSPATH: /Applications/jboss-3.2.3/bin/run.jar:/Library/Java/Home/../Classes/classes.jar

                  ================================================================================

                  16:11:00,450 INFO [Server] Starting JBoss (MX MicroKernel)...
                  16:11:00,454 INFO [Server] Release ID: JBoss [WonderLand] 3.2.3 (build: CVSTag=JBoss_3_2_3 date=200311301445)
                  16:11:00,456 INFO [Server] Home Dir: /Applications/jboss-3.2.3
                  16:11:00,459 INFO [Server] Home URL: file:/Applications/jboss-3.2.3/
                  16:11:00,461 INFO [Server] Library URL: file:/Applications/jboss-3.2.3/lib/
                  16:11:00,463 INFO [Server] Patch URL: null
                  16:11:00,490 INFO [Server] Server Name: default
                  16:11:00,492 INFO [Server] Server Home Dir: /Applications/jboss-3.2.3/server/default
                  16:11:00,493 INFO [Server] Server Home URL: file:/Applications/jboss-3.2.3/server/default/
                  16:11:00,494 INFO [Server] Server Data Dir: /Applications/jboss-3.2.3/server/default/data
                  16:11:00,495 INFO [Server] Server Temp Dir: /Applications/jboss-3.2.3/server/default/tmp
                  16:11:00,496 INFO [Server] Server Config URL: file:/Applications/jboss-3.2.3/server/default/conf/
                  16:11:00,497 INFO [Server] Server Library URL: file:/Applications/jboss-3.2.3/server/default/lib/
                  16:11:00,498 INFO [Server] Root Deployment Filename: jboss-service.xml
                  16:11:00,504 INFO [Server] Starting General Purpose Architecture (GPA)...
                  16:11:01,037 INFO [ServerInfo] Java version: 1.4.2_03,Apple Computer, Inc.
                  16:11:01,039 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2-34,"Apple Computer, Inc."
                  16:11:01,048 INFO [ServerInfo] OS-System: Mac OS X 10.3.2,ppc

                  This is extremely frustrating as I would LOVE to use JIKES and new features in JB3.2.3, but I can't move it to production with BLATANT compilation errors like this.

                  • 6. Re: JSP compilation error using regular javac in JB3.2.3
                    darranl

                    What happens with JBoss 3.2.3 with Jetty?

                    • 7. Re: JSP compilation error using regular javac in JB3.2.3
                      tbauer

                      It works great with jboss-3.2.3_jetty-4.2.14 so far..will continue testing...Disturbing tho, since JBG has ordained Tomcat as it's "official" web engine..

                      Also, since OS X has been out for almost 3 years now, it would be nice if someone could please fix the DEFAULT /bin/run.sh to point to the proper
                      OS X classes.jar file...

                      JAVAC_JAR="$JAVA_HOME/../Classes/classes.jar"

                      NOT

                      JAVAC_JAR="$JAVA_HOME/lib/tools.jar"

                      • 8. Re: JSP compilation error using regular javac in JB3.2.3
                        darranl

                        Also, since OS X has been out for almost 3 years now, it would be nice if someone could please fix the DEFAULT /bin/run.sh to point to the proper
                        OS X classes.jar file...


                        Has the bug been raised on sourceforge yet?

                        Other developers may not have experienced the problems that you are having so you may need to submit a patch with the version that works for you.

                        • 9. Re: JSP compilation error using regular javac in JB3.2.3
                          tbauer

                          I'll submit a bug about the /bin/run.sh parameter, but hopefully someone from JBoss Group could do some testing of JB3.2.3 (with and without Jikes) using OS X 10.3.2 and java 1.4.2...

                          Since JBoss is also distributed with the Apple Developer package, I'll also contact some friends inside Apple to see if they have encountered this problem or know about it...

                          Can't rely on this version(3.2.3 with Tomcat) until someone steps up to the plate with some answers.