geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GERONIMO-5919) WAB does not support jsp.
Date Wed, 20 Apr 2011 02:39:05 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jarek Gawor resolved GERONIMO-5919.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0-M2

The problem turned out to be in xbean-bundleutils in the updated BundleClassLoader implementation.
It was not always using the right bundle object to look for classes and resources. Fixed in
xbean in revision 1095196.

I also added a test case for JSPs in a WAB to Geronimo trunk in revision 1095217.


> WAB does not support jsp.
> -------------------------
>
>                 Key: GERONIMO-5919
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5919
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: Shawn Jiang
>            Assignee: Jarek Gawor
>             Fix For: 3.0-M2
>
>         Attachments: simple-wab-3.0-SNAPSHOT.jar
>
>
> 1, deploy the attached simple wab
> 2, access the simple jsp in it.  http://localhost:8080/simple/index.jsp
> 3, you could see following exception.
> Can't recreate if you deploy a similar war package.   I'm not sure if current web extender
has added the jsp servlet correctly to handle the jsp.
> ------------------------------------------------
> HTTP Status 500 - 
> type Exception report
> message
> description The server encountered an internal error () that prevented it from fulfilling
this request.
> exception
> org.apache.jasper.JasperException: Unable to compile class for JSP: 
> An error occurred at line: 7 in the generated java file
> org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type
> An error occurred at line: 8 in the generated java file
> org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type
> An error occurred at line: 10 in the generated java file
> JspFactory cannot be resolved to a type
> An error occurred at line: 10 in the generated java file
> JspFactory cannot be resolved
> An error occurred at line: 14 in the generated java file
> javax.el.ExpressionFactory cannot be resolved to a type
> An error occurred at line: 15 in the generated java file
> org.apache.tomcat.InstanceManager cannot be resolved to a type
> An error occurred at line: 22 in the generated java file
> _el_expressionfactory cannot be resolved
> An error occurred at line: 22 in the generated java file
> _jspxFactory cannot be resolved
> An error occurred at line: 22 in the generated java file
> The method getServletConfig() is undefined for the type index_jsp
> An error occurred at line: 23 in the generated java file
> _jsp_instancemanager cannot be resolved
> An error occurred at line: 23 in the generated java file
> org.apache.jasper.runtime.InstanceManagerFactory cannot be resolved to a type
> An error occurred at line: 23 in the generated java file
> The method getServletConfig() is undefined for the type index_jsp
> An error occurred at line: 32 in the generated java file
> PageContext cannot be resolved to a type
> An error occurred at line: 36 in the generated java file
> JspWriter cannot be resolved to a type
> An error occurred at line: 38 in the generated java file
> JspWriter cannot be resolved to a type
> An error occurred at line: 39 in the generated java file
> PageContext cannot be resolved to a type
> An error occurred at line: 44 in the generated java file
> _jspxFactory cannot be resolved
> An error occurred at line: 81 in the generated java file
> SkipPageException cannot be resolved to a type
> An error occurred at line: 88 in the generated java file
> _jspxFactory cannot be resolved
> Stacktrace:
> 	org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92)
> 	org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330)
> 	org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:443)
> 	org.apache.jasper.compiler.Compiler.compile(Compiler.java:367)
> 	org.apache.jasper.compiler.Compiler.compile(Compiler.java:345)
> 	org.apache.jasper.compiler.Compiler.compile(Compiler.java:332)
> 	org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:594)
> 	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:327)
> 	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:363)
> 	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:306)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> note The full stack trace of the root cause is available in the Apache Tomcat/7.0.0.2-SNAPSHOT
logs.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message