Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Batch Datasource Generator Does Not Work: SC_SNAPSHOT-2011-07-18/EVAL Deployment

    Max OS/X 10.6.8 -- SpringSource Toolsuite 2.7.1 on top of Eclipse 3.6 -- gwt-2.3.0 -- Java 6

    Here is the console output from Eclipse when I try to generate datasources:

    Code:
    [WARN] /builtinds/tools/batchDSGenerator.jsp
    Compile failed; see the compiler error output for details.
    	at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:933)
    	at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:757)
    	at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:382)
    	at org.apache.jasper.compiler.Compiler.compile(Compiler.java:472)
    	at org.apache.jasper.compiler.Compiler.compile(Compiler.java:451)
    	at org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
    	at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
    	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
    	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
    	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1097)
    	at com.isomorphic.servlet.CompressionFilter.doFilter(CompressionFilter.java:259)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1088)
    	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
    	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
    	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:49)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.Server.handle(Server.java:324)
    	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
    	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:829)
    	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
    	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
    	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
    	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
    	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488)

    #2
    Don't leave us in suspense - what's the compiler output that this warning message tells you to look at?

    Comment


      #3
      Not sure I follow you.

      All that was done was SCEE.openDataSourceGenerator() from the builtinds sample app. Attached is a screenshot snippet of the generator. The console output is produced when I hit "ok."

      Can you explain where I can look for this compiler output?
      Attached Files

      Comment


        #4
        Typically, if you get a compile error, the actual compilation error is right there in the same log file (that's what Jetty is telling you).

        With the message you're showing, we have no information about what is causing the compile error. Typical problems would be missing .jar files, mixed versions, things like that.

        Comment


          #5
          Thanks for your reply.

          I simply do not know where to look, and I have not been able to find a reference on-line for where the embedded jetty places its log files.

          I think this error is easy to reproduce:

          (0) configure a shortcut key to invoke SCEE.showDataSourceGenerator() in the builtinds sample;
          (1) run the war target in build.xml;
          (2) run builtinds with gpe from within eclipse;
          (3) invoke the datasource generator with the shortcut key defined in (0);
          (4) select database HSQLDB;
          (5) select table "ANIMALS;" and
          (6) click "OK."

          Comment


            #6
            We finally nailed this. It's specific to Jetty + GWT hosted mode and is not a problem in any other engine or in compiled mode. Incredibly, Jetty barfs on Java 1.5 constructs in .jsp code for no reason (as mentioned here).

            Further, we also could not find a way to get Jetty to actually report what the compilation problem was, despite extensive efforts.

            But this is fixed for the next build.

            Comment


              #7
              Hello,
              I see you said you fixed this back in July, but I am having the same problem as wil.pannell. The error log generated inside of eclipse GEP is identical to the one he posted. I am using the SmartGwtEE evaluation that I just downloaded last week. SC_SNAPSHOT-2012-03-02_v8.2p/EVAL Development. As wil stated, I do not see any further compiler output. I am using Eclipse Indigo with the GEP GWT 2.4.

              Comment


                #8
                Nevermind, I have fixed the issue. I manually copied all of the jars from the smartgwt dist's lib folder into the project's war/WEB-INF/lib folder. This was a little confusing because I was doing it with the HibernateSpringDMI sample project, the project itself ran fine before I copied these jars, but the DataSource Generator would not work. You may want to make that more clear in the example's readme.

                Comment

                Working...
                X