portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27755] New: - Jetspeed fails to display JSPs correctly
Date Wed, 17 Mar 2004 18:58:48 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27755>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27755

Jetspeed fails to display JSPs correctly

           Summary: Jetspeed fails to display JSPs correctly
           Product: Jetspeed
           Version: 1.4
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: JSP
        AssignedTo: jetspeed-dev@jakarta.apache.org
        ReportedBy: factor3@rcn.com


Am running Jetspeed 1.4 under Tomcat 4. 

1. Configured Jetspeed to display its "bottomnav" using a JSP file (in the
JetspeedResources.properties file, change "bottomnav.vm so it is equal to
"copyright.jsp"). The file copyright.jsp contains the following:

<table border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td class="small">
<div align="center">Copyright &copy; 2003 by Factor Three Webworks, LLC</div>
<hr size="1">
<div align="center">Web Design by <a href="http://www.webdex.com/"
target="_blank">Webdex, Inc.</a></div>
</td>
</tr>
</table>

Ran Tomcat with the JSP in the proper place in the templates folder. Jetspeed
actually displays the text and links in the copyright.jsp file, but it also
displays the following:

Error processing navigation template:/html/copyright.jsp using module:
BaseJspNavigation

2. Maintained the configuration described above, but changed the copyright.jsp
file so that it contains the entire contents of "bottom.jsp" (a file that is
provided with Jetspeed). Redisplayed and got the following:

 Error encountered processing a template:
/navigations//html/bottom.jsporg.apache.jasper.JasperException at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:575)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:498)
at
org.apache.turbine.services.jsp.TurbineJspService.handleRequest(TurbineJspService.java:202)
at
org.apache.turbine.services.jsp.TurbineJspService.handleRequest(TurbineJspService.java:163)
at
org.apache.turbine.modules.navigations.BaseJspNavigation.buildTemplate(BaseJspNavigation.java:91)
at
org.apache.turbine.modules.navigations.TemplateNavigation.doBuild(TemplateNavigation.java:103)
at org.apache.turbine.modules.Navigation.build(Navigation.java:98) at
org.apache.turbine.modules.NavigationLoader.eval(NavigationLoader.java:129) at
org.apache.turbine.util.template.TemplateNavigation.toString(TemplateNavigation.java:125)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:321)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:94) at
org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:109)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:271)
at org.apache.velocity.Template.merge(Template.java:296) at
org.apache.velocity.app.Velocity.mergeTemplate(Velocity.java:492) at
org.apache.velocity.app.Velocity.mergeTemplate(Velocity.java:461) at
org.apache.turbine.services.velocity.TurbineVelocityService.decodeRequest(TurbineVelocityService.java:494)
at
org.apache.turbine.services.velocity.TurbineVelocityService.handleRequest(TurbineVelocityService.java:336)
at
org.apache.turbine.services.velocity.TurbineVelocity.handleRequest(TurbineVelocity.java:143)
at
org.apache.turbine.modules.layouts.VelocityDirectLayout.doBuild(VelocityDirectLayout.java:106)
at org.apache.turbine.modules.Layout.build(Layout.java:91) at
org.apache.turbine.modules.LayoutLoader.exec(LayoutLoader.java:123) at
org.apache.turbine.modules.pages.DefaultPage.doBuild(DefaultPage.java:169) at
org.apache.turbine.modules.Page.build(Page.java:90) at
org.apache.turbine.modules.PageLoader.exec(PageLoader.java:123) at
org.apache.turbine.Turbine.doGet(Turbine.java:563) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601) at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:534) Error processing navigation
template:/html/bottom.jsp using module: BaseJspNavigation

Clearly, something is incorrect in the way Jetspeed is handling the JSP files.

Jetspeed documentation claims that Jetspeed is capable of using Velocity files
*and* JSPs as templates for various parts of its display. It even supplies us
with VM and JSP files in its template directories. Unfortunately, its entire
configuration appears to be oriented towards the use of Velocity files; there is
nothing in the documentation that tells us how to configure it to use JSPs.
Worse, attempts to use JSPs with Jetspeed appear to cause errors. It does not
appear that claims to allow users to use JSPs for templates are entirely accurate.

One of three things must be done here:

1: If the problem is in Jetspeed's JSP reader, then the reader must be debugged
and fixed -- at least to the point where it is able to handle JSPs that you
supply with the application!

or

2: If there is some other configuration step required to make Jetspeed properly
handle JSPs, it needs to be documented so that people won't screw up the system
every time they try to utilize a JSP- based template. Right now, best guesses at
how to use JSP templates are not enough. In fact, it would help greatly if an
example using JSP templates was added to the documentation.

or

3: If Jetspeed is really not supposed to be handling JSP templates, then all the
sample JSP templates should be eliminated and the documentation should be
changed to reflect this.

Thank you.

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org


Mime
View raw message