[appengine-java] Re: Problem switching to 1.4.0 - JSP compilation fails
no luck :( On Saturday, December 18, 2010 4:12:05 AM UTC+1, Helder Suzuki wrote: > > Hi Lorenzo, > > I was having this problem too. > > This will fix it in the development environment: > > 1) Open appengine-java-sdk-1.4.0.zip > 2) Find el-api.jar, jsp-api.jar, servlet-api.jar and > repackaged-appengine-jasper-6.0.29.jar > 3) Copy them to war/WEB-INF/lib > > Thanks, > Helder > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Problem switching to 1.4.0 - JSP compilation fails
Thank you, I'll try it as soon as possible. I did try to use the jars from a standard J2ee distribution (not repackaged), but that did not work since some libraries were still missing. Thanks for your suggestion, this will be really helpful. Lorenzo On Dec 18, 4:12 am, Helder Suzuki wrote: > Hi Lorenzo, > > I was having this problem too. > > This will fix it in the development environment: > > 1) Open appengine-java-sdk-1.4.0.zip > 2) Find el-api.jar, jsp-api.jar, servlet-api.jar and > repackaged-appengine-jasper-6.0.29.jar > 3) Copy them to war/WEB-INF/lib > > Thanks, > Helder -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Problem switching to 1.4.0 - JSP compilation fails
Hi Lorenzo, I was having this problem too. This will fix it in the development environment: 1) Open appengine-java-sdk-1.4.0.zip 2) Find el-api.jar, jsp-api.jar, servlet-api.jar and repackaged-appengine-jasper-6.0.29.jar 3) Copy them to war/WEB-INF/lib Thanks, Helder -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Problem switching to 1.4.0 - JSP compilation fails
Thank you for the link. I tried to deploy a test app and everything works correctly in production. I'll live with the bug in the devserver, just go to the emulated login page by hand. Thanks Lorenzo On Dec 10, 11:41 am, Thomas Meyer wrote: > The problem has also been discussed here (the newer > entries):http://groups.google.com/group/google-appengine-java/browse_thread/th... > > And there's an issue you can > star:http://code.google.com/p/googleappengine/issues/detail?id=4216 > > I can also confirm that the problem only exists locally on the > development server. If you deploy it to the app engine servers the > mappings will work. > > Best, Thomas > > On Dec 10, 9:10 am, "l.denardo" wrote: > > > Thank you Ikay and Starman. > > I'll try to use auto mapping, and verify everything's fine in > > production. > > > I can confirm not-mapped JSP pages work correctly in dev, the mapping > > I use is just for the openID login page. > > I'll try and see if I can use something different to produce my login > > page, but if this is only for the dev server I can bypass this simply > > since login page address is different. > > > I also hit the problem of static files not being filtered (I guess you > > are using spring security :-)), I ended up using real JSP since I > > customize the host page with email address and logout link from User > > service. > > > Thank you again for your help. > > Regards > > Lorenzo > > > On Dec 10, 6:01 am, Starman wrote: > > > > I was using a servlet mapping to make my url nicer. Instead of > > > appid.appspot.com/MyApp.jsp, I had appid.appspot.com/servletname. And > > > I was using the jsp-file tag to map the servlet to the jsp file. > > > > I have commented out the servlet definition and just let the jsp auto > > > mapping do its thing. And everything works fine, albeit with uglier > > > urls. > > > > Btw, I'm using a jsp for my GWT host file instead of an html file so > > > that I can secure the app host file. Html being statically deployed > > > makes it impossible to secure at the servlet layer. > > > > R. > > > > On Dec 9, 6:03 pm, "Ikai Lan (Google)" > > > wrote: > > > > > We're reproduced this. It seems to happen when you map a URL to a JSP, > > > > and > > > > only on the development server. > > > > > -- > > > > Ikai Lan > > > > Developer Programs Engineer, Google App Engine > > > > Blogger:http://googleappengine.blogspot.com > > > > Reddit:http://www.reddit.com/r/appengine > > > > Twitter:http://twitter.com/app_engine > > > > > On Thu, Dec 9, 2010 at 8:36 AM, l.denardo > > > > wrote: > > > > > Hello, > > > > > I'm having trouble switching to 1.4.0 SDK. > > > > > > Development server starts regularly, but when I try to load my login > > > > > page (a jsp file) I get the following error: > > > > > > [WARN] /_ah/login_required > > > > > org.apache.jasper.JasperException: Unable to compile class for JSP: > > > > > > An error occurred at line: 1 in the generated java file > > > > > The type javax.servlet.jsp.PageContext cannot be resolved. It is > > > > > indirectly referenced from required .class files > > > > > > An error occurred at line: 1 in the generated java file > > > > > The type javax.servlet.jsp.tagext.TagSupport cannot be resolved. It is > > > > > indirectly referenced from required .class files > > > > > > [more similar entries follow] > > > > > > An error occurred at line: 1,079 in the generated java file > > > > > javax.servlet.jsp.tagext.JspTag cannot be resolved to a type > > > > > > Stacktrace: > > > > > at > > > > > > org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandl > > > > > er.java: > > > > > 92) > > > > > at > > > > > org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: > > > > > 330) > > > > > at > > > > > org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: > > > > > 439) > > > > > at > > > > > org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) > > > > > at > > > > > org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) > > > > > at > > > > > org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) > > > > > at > > > > > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: > > > > > 592) > > > > > at > > > > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java: > > > > > 317) > > > > > at > > > > > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java: > > > > > 313) > > > > > at > > > > > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260) > > > > > at > > > > > com.google.appengine.tools.development.PrivilegedJspServlet.access > > > > > $101(PrivilegedJspServlet.java:23) > > > > > at com.google.appengine.tools.development.PrivilegedJspServlet > > > > > $2.run(PrivilegedJspServlet.java:59) > > > > > at java.security.AccessController.doPrivileged(Native Method) > > > > > at > > > >
[appengine-java] Re: Problem switching to 1.4.0 - JSP compilation fails
The problem has also been discussed here (the newer entries): http://groups.google.com/group/google-appengine-java/browse_thread/thread/dd17f4150950374c And there's an issue you can star: http://code.google.com/p/googleappengine/issues/detail?id=4216 I can also confirm that the problem only exists locally on the development server. If you deploy it to the app engine servers the mappings will work. Best, Thomas On Dec 10, 9:10 am, "l.denardo" wrote: > Thank you Ikay and Starman. > I'll try to use auto mapping, and verify everything's fine in > production. > > I can confirm not-mapped JSP pages work correctly in dev, the mapping > I use is just for the openID login page. > I'll try and see if I can use something different to produce my login > page, but if this is only for the dev server I can bypass this simply > since login page address is different. > > I also hit the problem of static files not being filtered (I guess you > are using spring security :-)), I ended up using real JSP since I > customize the host page with email address and logout link from User > service. > > Thank you again for your help. > Regards > Lorenzo > > On Dec 10, 6:01 am, Starman wrote: > > > > > > > > > I was using a servlet mapping to make my url nicer. Instead of > > appid.appspot.com/MyApp.jsp, I had appid.appspot.com/servletname. And > > I was using the jsp-file tag to map the servlet to the jsp file. > > > I have commented out the servlet definition and just let the jsp auto > > mapping do its thing. And everything works fine, albeit with uglier > > urls. > > > Btw, I'm using a jsp for my GWT host file instead of an html file so > > that I can secure the app host file. Html being statically deployed > > makes it impossible to secure at the servlet layer. > > > R. > > > On Dec 9, 6:03 pm, "Ikai Lan (Google)" > > wrote: > > > > We're reproduced this. It seems to happen when you map a URL to a JSP, and > > > only on the development server. > > > > -- > > > Ikai Lan > > > Developer Programs Engineer, Google App Engine > > > Blogger:http://googleappengine.blogspot.com > > > Reddit:http://www.reddit.com/r/appengine > > > Twitter:http://twitter.com/app_engine > > > > On Thu, Dec 9, 2010 at 8:36 AM, l.denardo > > > wrote: > > > > Hello, > > > > I'm having trouble switching to 1.4.0 SDK. > > > > > Development server starts regularly, but when I try to load my login > > > > page (a jsp file) I get the following error: > > > > > [WARN] /_ah/login_required > > > > org.apache.jasper.JasperException: Unable to compile class for JSP: > > > > > An error occurred at line: 1 in the generated java file > > > > The type javax.servlet.jsp.PageContext cannot be resolved. It is > > > > indirectly referenced from required .class files > > > > > An error occurred at line: 1 in the generated java file > > > > The type javax.servlet.jsp.tagext.TagSupport cannot be resolved. It is > > > > indirectly referenced from required .class files > > > > > [more similar entries follow] > > > > > An error occurred at line: 1,079 in the generated java file > > > > javax.servlet.jsp.tagext.JspTag cannot be resolved to a type > > > > > Stacktrace: > > > > at > > > > > org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandl > > > > er.java: > > > > 92) > > > > at > > > > org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: > > > > 330) > > > > at > > > > org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: > > > > 439) > > > > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) > > > > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) > > > > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) > > > > at > > > > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: > > > > 592) > > > > at > > > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java: > > > > 317) > > > > at > > > > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java: > > > > 313) > > > > at > > > > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260) > > > > at > > > > com.google.appengine.tools.development.PrivilegedJspServlet.access > > > > $101(PrivilegedJspServlet.java:23) > > > > at com.google.appengine.tools.development.PrivilegedJspServlet > > > > $2.run(PrivilegedJspServlet.java:59) > > > > at java.security.AccessController.doPrivileged(Native Method) > > > > at > > > > > com.google.appengine.tools.development.PrivilegedJspServlet.service(Privile > > > > gedJspServlet.java: > > > > 57) > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > > > > at > > > > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: > > > > 511) > > > > at org.mortbay.jetty.servlet.ServletHandler > > > > $CachedChain.doFilter(ServletHandler.java:1166) > > > > at > > > > > co
[appengine-java] Re: Problem switching to 1.4.0 - JSP compilation fails
Thank you Ikay and Starman. I'll try to use auto mapping, and verify everything's fine in production. I can confirm not-mapped JSP pages work correctly in dev, the mapping I use is just for the openID login page. I'll try and see if I can use something different to produce my login page, but if this is only for the dev server I can bypass this simply since login page address is different. I also hit the problem of static files not being filtered (I guess you are using spring security :-)), I ended up using real JSP since I customize the host page with email address and logout link from User service. Thank you again for your help. Regards Lorenzo On Dec 10, 6:01 am, Starman wrote: > I was using a servlet mapping to make my url nicer. Instead of > appid.appspot.com/MyApp.jsp, I had appid.appspot.com/servletname. And > I was using the jsp-file tag to map the servlet to the jsp file. > > I have commented out the servlet definition and just let the jsp auto > mapping do its thing. And everything works fine, albeit with uglier > urls. > > Btw, I'm using a jsp for my GWT host file instead of an html file so > that I can secure the app host file. Html being statically deployed > makes it impossible to secure at the servlet layer. > > R. > > On Dec 9, 6:03 pm, "Ikai Lan (Google)" > wrote: > > > We're reproduced this. It seems to happen when you map a URL to a JSP, and > > only on the development server. > > > -- > > Ikai Lan > > Developer Programs Engineer, Google App Engine > > Blogger:http://googleappengine.blogspot.com > > Reddit:http://www.reddit.com/r/appengine > > Twitter:http://twitter.com/app_engine > > > On Thu, Dec 9, 2010 at 8:36 AM, l.denardo wrote: > > > Hello, > > > I'm having trouble switching to 1.4.0 SDK. > > > > Development server starts regularly, but when I try to load my login > > > page (a jsp file) I get the following error: > > > > [WARN] /_ah/login_required > > > org.apache.jasper.JasperException: Unable to compile class for JSP: > > > > An error occurred at line: 1 in the generated java file > > > The type javax.servlet.jsp.PageContext cannot be resolved. It is > > > indirectly referenced from required .class files > > > > An error occurred at line: 1 in the generated java file > > > The type javax.servlet.jsp.tagext.TagSupport cannot be resolved. It is > > > indirectly referenced from required .class files > > > > [more similar entries follow] > > > > An error occurred at line: 1,079 in the generated java file > > > javax.servlet.jsp.tagext.JspTag cannot be resolved to a type > > > > Stacktrace: > > > at > > > > org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java: > > > 92) > > > at > > > org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: > > > 330) > > > at > > > org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: > > > 439) > > > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) > > > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) > > > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) > > > at > > > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: > > > 592) > > > at > > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java: > > > 317) > > > at > > > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java: > > > 313) > > > at > > > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260) > > > at > > > com.google.appengine.tools.development.PrivilegedJspServlet.access > > > $101(PrivilegedJspServlet.java:23) > > > at com.google.appengine.tools.development.PrivilegedJspServlet > > > $2.run(PrivilegedJspServlet.java:59) > > > at java.security.AccessController.doPrivileged(Native Method) > > > at > > > > com.google.appengine.tools.development.PrivilegedJspServlet.service(PrivilegedJspServlet.java: > > > 57) > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > > > at > > > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: > > > 511) > > > at org.mortbay.jetty.servlet.ServletHandler > > > $CachedChain.doFilter(ServletHandler.java:1166) > > > at > > > > com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java: > > > 58) > > > at org.mortbay.jetty.servlet.ServletHandler > > > $CachedChain.doFilter(ServletHandler.java:1157) > > > at > > > > com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java: > > > 43) > > > at org.mortbay.jetty.servlet.ServletHandler > > > $CachedChain.doFilter(ServletHandler.java:1157) > > > at > > > > com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java: > > > 122) > > > at org.mortbay.jetty.servlet.ServletHandler > > > $CachedChain.doFilter(ServletHandler.java:1157) > >
[appengine-java] Re: Problem switching to 1.4.0 - JSP compilation fails
I was using a servlet mapping to make my url nicer. Instead of appid.appspot.com/MyApp.jsp, I had appid.appspot.com/servletname. And I was using the jsp-file tag to map the servlet to the jsp file. I have commented out the servlet definition and just let the jsp auto mapping do its thing. And everything works fine, albeit with uglier urls. Btw, I'm using a jsp for my GWT host file instead of an html file so that I can secure the app host file. Html being statically deployed makes it impossible to secure at the servlet layer. R. On Dec 9, 6:03 pm, "Ikai Lan (Google)" wrote: > We're reproduced this. It seems to happen when you map a URL to a JSP, and > only on the development server. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > Blogger:http://googleappengine.blogspot.com > Reddit:http://www.reddit.com/r/appengine > Twitter:http://twitter.com/app_engine > > > > On Thu, Dec 9, 2010 at 8:36 AM, l.denardo wrote: > > Hello, > > I'm having trouble switching to 1.4.0 SDK. > > > Development server starts regularly, but when I try to load my login > > page (a jsp file) I get the following error: > > > [WARN] /_ah/login_required > > org.apache.jasper.JasperException: Unable to compile class for JSP: > > > An error occurred at line: 1 in the generated java file > > The type javax.servlet.jsp.PageContext cannot be resolved. It is > > indirectly referenced from required .class files > > > An error occurred at line: 1 in the generated java file > > The type javax.servlet.jsp.tagext.TagSupport cannot be resolved. It is > > indirectly referenced from required .class files > > > [more similar entries follow] > > > An error occurred at line: 1,079 in the generated java file > > javax.servlet.jsp.tagext.JspTag cannot be resolved to a type > > > Stacktrace: > > at > > > org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java: > > 92) > > at > > org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: > > 330) > > at > > org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: > > 439) > > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) > > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) > > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) > > at > > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: > > 592) > > at > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java: > > 317) > > at > > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java: > > 313) > > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260) > > at > > com.google.appengine.tools.development.PrivilegedJspServlet.access > > $101(PrivilegedJspServlet.java:23) > > at com.google.appengine.tools.development.PrivilegedJspServlet > > $2.run(PrivilegedJspServlet.java:59) > > at java.security.AccessController.doPrivileged(Native Method) > > at > > > com.google.appengine.tools.development.PrivilegedJspServlet.service(PrivilegedJspServlet.java: > > 57) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > > at > > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: > > 511) > > at org.mortbay.jetty.servlet.ServletHandler > > $CachedChain.doFilter(ServletHandler.java:1166) > > at > > > com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java: > > 58) > > at org.mortbay.jetty.servlet.ServletHandler > > $CachedChain.doFilter(ServletHandler.java:1157) > > at > > > com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java: > > 43) > > at org.mortbay.jetty.servlet.ServletHandler > > $CachedChain.doFilter(ServletHandler.java:1157) > > at > > > com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java: > > 122) > > at org.mortbay.jetty.servlet.ServletHandler > > $CachedChain.doFilter(ServletHandler.java:1157) > > at > > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: > > 388) > > at > > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java: > > 216) > > at > > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java: > > 182) > > at > > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java: > > 765) > > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: > > 418) > > at > > > com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java: > > 70) > > at > > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: > > 152) > > at com.google.appengine.tools.development.JettyContainerService > > $ApiProxyHandler.handle(JettyContainerService.java:349) > > at > > org.mortbay.jetty.handler.Handler
