Hi James. Are you using the latest version of the SDK?
I use <jsp:include> in a few of my projects and I haven't seen an exception
yet in either the local or production environments, so I don't think the
include tag itself is the issue. It's certainly possible that the included
JSP has an error which is getting bubbled up as this other exception. Can
you narrow this down any more?
- Jason
On Fri, Sep 18, 2009 at 11:26 AM, James H <james.hollier...@gmail.com>wrote:
>
> Jayson, the include in my JSP looks like this:
>
> jsp:include page="homeLeft.jsp" flush="true"
>
> I assume the Google plugin for Eclipse is handling this in a
> compatible manner between the test environment provided by the plugin
> versus production. So, I'm not sure what to change by your comment on
> "include". I did miss the try/catch there...I'll try that next.
> Thanks, J
>
> On Sep 18, 12:41 pm, Jayson Falkner <jfalk...@gmail.com> wrote:
> > You could catch this exception to find out more about it; however, I
> > think you just need to use the normal Servlet RequestDispatcher
> > instead of Apache's specific implementation. e.g.
> >
> > request.getRequestDispatcher().include(request, response);
> >
> > Note that the JSP/Servlet spec doesn't require Apache. Meaning you
> > should stick to the spec's classes and interfaces if you expect your
> > code to work between possibly different containers.
> >
> > Hope it helps,
> >
> > Jayson
> >
> >
> >
> > On Thu, Sep 17, 2009 at 10:09 PM, James H <james.hollier...@gmail.com>
> wrote:
> >
> > > This cast exception is NOT obvious. Here's the production stack
> > > snippet:
> >
> > > /homeIndex.jsp
> > > java.lang.ClassCastException: java.lang.ClassCastException cannot be
> > > cast to javax.servlet.ServletException
> > > at org.apache.jasper.runtime.PageContextImpl.handlePageException
> > > (PageContextImpl.java:754)
> > > at
> org.apache.jsp.homeIndex_jsp._jspService(homeIndex_jsp.java:67)
> > > at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> > > at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
> > > 487)
> > > at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
> > > ...
> >
> > > And here's the homeIndex_jsp.java (from my local runtime test
> > > environment). Line 67 is the last one listed here:
> >
> > > ...
> > > out.write("\t\t\t\t<tr>\n");
> > > out.write("\t\t\t\t\t<td>\n");
> > > org.apache.jasper.runtime.JspRuntimeLibrary.include(request,
> > > response, "homeLeft.jsp", out, true);
> > > out.write("\n");
> > > ...
> >
> > > Any ideas on how a class cast exception could occur above? Naturally,
> > > this runs fine in my test environment but NOT in production!
> >
> > > Thanks, J- Hide quoted text -
> >
> > - Show quoted text -
> >
>
--~--~---------~--~----~------------~-------~--~----~
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-java@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
-~----------~----~----~----~------~----~------~--~---
