DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22316>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22316 Double slash causes error for JSP templates in Websphere Summary: Double slash causes error for JSP templates in Websphere Product: Jetspeed Version: 1.4b4 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: JSP AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Using JSP instead of Velocity templates in Jetspeed fails with the Websphere 5.0 Test Environment in WSAD because of a double-slash in the resource path. The Turbine 2.2 class, org.apache.turbine.modules.navigations.BaseJspNavigation (method buildTemplate(RunData)) generates a path to a resource by adding the hard-coded string "/navigations/" to the beginning of the template name. JetspeedTemplateLocatorService class has a hard-coded "/navigations", used when it checks for the existence of the template file before BaseJspNavigation attempts to access it. The JetspeedTemplateLocatorService is also the class responsible for returning the part of the path immediately before the file name (to enable localization). This functionality matches the hard-coded "/navigations" that is present in the Jetspeed class, instead of matching what Turbine expects. This causes its paths to work fine when the whole path is retrieved in the class, but when combined with the Turbine BaseJspNavigation functionality (part of the actual JSP call), a double slash results. Tomcat ignores this double slash and serves the page with no problem, but Websphere 5.0 fails with the following error: Error encountered processing a template: /navigations//html/top_default.jspjavax.servlet.ServletException: /WEB-INF/templates/jsp/navigations//html/top_default.jsp at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:365) at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:598) at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:696) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110) at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174) at com.ibm.ws.webcontainer.servlet.ServicingServletState.service(StrictLifecycleServlet.java:333) at <snip>com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:331) at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56) at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:432) at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:343) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592) Error processing navigation template: top_default.jsp using module: BaseJspNavigation I changed the hard-coded String in Turbine's BaseJspNavigation to "/navigations" and my jsp templates now work perfectly in WSAD. I think this is the wrong way to fix the problem permanently, however--Jetspeed should be modified to work with Turbine, not the other way around! :) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
