Hey Rajeev,
Yes when I went to hit my JSP files in the google hosted browser it
would fail with the message "Unable to compile class for JSP". There
was nothing descriptive in the hosted browser log about why it had
failed to compile. All of the error messages said to refer to the
compiler error output, which as far as I can tell isn't logged
anywhere accessible.
Note that the JSP would compile correctly if I avoided any scriptlet
references to my classes (despite having proper imports), so I would
guess it had something to do with the classpath being used for the Ant
compiler invoked for compiling the JSP-> java generated files.
With App Engine enabled for the project I could compile correctly, so
whatever classpath issue might have affected the GWT-only compilation
did not have any effect here. But then of course I was left with the
issue which started this discussion, so I made my little workaround
(which is working beautifully so far).
With App Engine unchecked, the most interesting log message I see in
my hosted mode console is the following:
[SPAM] EXCEPTION
org.apache.jasper.JasperException: Unable to compile class for JSP
at org.apache.jasper.compiler.DefaultErrorHandler.javacError
(DefaultErrorHandler.java:97)
at org.apache.jasper.compiler.ErrorDispatcher.javacError
(ErrorDispatcher.java:346)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:
414)
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.handle
(ServletHandler.java:362)
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:320)
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)
Caused by: org.apache.tools.ant.BuildException: 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.handle
(ServletHandler.java:362)
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:320)
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)
On Jul 8, 11:54 am, Rajeev Dayal <[email protected]> wrote:
> Hi,
> When you say that the JSP files would not compile, how were you trying to
> compile them? Were you hitting the JSP in a browser?
>
> Rajeev
>
> On Tue, Jul 7, 2009 at 10:37 PM, puddlesofjoy <[email protected]> wrote:
>
> > Additional information for those who have this same problem and find
> > this post like I did.
> > Using Eclipse 3.4.2, Google Eclipse Plugin 1.0.1.v200905131143, GWT
> > 1.6.4, App Engine Java SDK 1.2.1
>
> > I faced two issues when trying to develop my JSP web application
> > (which uses JDBC and is not intended to be deployed on Google App
> > Engine; it just uses GWT)
>
> > - With App Engine enabled for the project it would compile my JSPs
> > correctly but give the security errors noted above
> > - With App Engine disabled (only gwt enabled) the JSP files would not
> > compile with the error "org.apache.jasper.JasperException: Unable to
> > compile class for JSP" and referencing me to the Compile Error Output
> > which does not seem to be available anywhere I can find...
>
> > My work around hack:
> > Extract appengine-java-sdk-1.2.1\libappengine-tools-api.jar
> > Use JBE (Java Bytecode Editor) to edit com\google\appengine\tools
> > \development\DevAppServerFactory$CustomSecurityManager.class
> > Empty out the check* functions so they only contain a 'return'
> > Jar back up and replace the original libappengine jar
>
> > I can now leave App Engine enabled and have no more security errors
> > AND my JSP files compile correctly! Huzzah!!
> > Note that of course this app could NOT be deployed to google app
> > engine. The App engine is just enabled since it allows my JSPs to
> > compile correctly.
>
> > Regards
>
> > On Jun 16, 12:35 pm, Khoa <[email protected]> wrote:
> > > Another soul is saved -- thank you
>
> > > On Jun 7, 8:34 am, aydogdu <[email protected]> wrote:
>
> > > > god bless you
>
> > > > On Apr 13, 2:46 pm, martin <[email protected]> wrote:
>
> > > > > Ok, I solved the problem ;-)
>
> > > > > Go to the project's properties and uncheck "Use Google App Engine".
> > > > > Additionally, as vitali mentioned, the mysql-connector jar has to be
> > > > > in the war/WEB-INF/lib directory.
> > > > > Cheers,
>
> > > > > Martin.
>
> > > > > On Apr 12, 3:16 pm, IvanRdz <[email protected]> wrote:
>
> > > > > > I have the same problem and I am sure it´s due to Jetty and
> > security
> > > > > > settings as you have mentioned. Are you using google plugin?
>
> > > > > > On Apr 11, 7:59 pm, martin <[email protected]> wrote:
>
> > > > > > > Ok, I am still stuck :-(
> > > > > > > Anybody got Mysql working with GWT 1.6.4? It worked fine for GWT
> > 1.5
> > > > > > > for me, but something seems to have changed with GWT 1.6.4.
> > > > > > > Maybe it is due to Jetty and security settings, since I get a
> > > > > > > "java.security.AccessControlException"... All I did was to add
> > the "/
> > > > > > > usr/share/java/mysql-connector-java-5.1.6.jar" to the referenced
> > > > > > > libraries.
>
> > > > > > > Please help me out!
> > > > > > > Thanks,
> > > > > > > Martin.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
