DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-08-15 19:49 --- You likely have a problem compiling JSPs. This works for me. Please don't reopen the bug, unless you can make a more convincing argument there's a Tomcat flaw. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2003-08-16 02:06 --- Remy, Ok, I'm sure I would have noticed if my normal JSP weren't compiling but just to be sure about whether JSPs would compile, I just now went through and clicked on all the JSP examples provided with Tomcat 5.0.7 and every one of them is working just fine. Granted they're not too complicated but I'm not seeing any problem at all compiling JSPs so far with 5.0.7. I went and dropped the original jetspeed.war into webapps and then added a JSP Portlet and received the same error as I reported above. This time I noticed another exception in the log that may help: INFO: Server startup in 20610 ms java.lang.IllegalArgumentException: -82 at org.apache.jasper.compiler.SmapStratum$LineInfo.setOutputLineIncrement(SmapStratum.java:124) at org.apache.jasper.compiler.SmapStratum.optimizeLineSection(SmapStratum.java:221) at org.apache.jasper.compiler.SmapUtil.evaluateNodes(SmapUtil.java:490) at org.apache.jasper.compiler.SmapUtil.generateSmap(SmapUtil.java:123) at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:301) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:453) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:555) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:300) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:293) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:286) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:752) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:640) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:552) 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.jetspeed.portal.portlets.viewprocessor.JSPViewProcessor.processView(JSPViewProcessor.java:170) at org.apache.jetspeed.portal.portlets.GenericMVCPortlet.buildContent(GenericMVCPortlet.java:301) at org.apache.jetspeed.portal.portlets.GenericMVCPortlet.getContent(GenericMVCPortlet.java:219) at org.apache.jetspeed.portal.security.portlets.PortletWrapper.getContent(PortletWrapper.java:148) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:260) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:207) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:250) 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.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
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-08-16 02:23 --- IllegalArgumentException in setOutputLineIncrement() is Bugzilla Bug 22277, and is fixed in CVS. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Additional Comments From [EMAIL PROTECTED] 2003-08-14 14:16 --- Re-opening the bug. Setup: RedHat Linux 8.0 J2SE 1.4.2 Tomcat 5.0.7-alpha Jetspeed 1.4-b4(release) and 1.4-b5-dev(from CVS) I downloaded the new version of Tomcat 5.0.7-alpha that included the fix for this bug and began testing it this morning. There are still problems with the JSP Portlet compilation: Here is the error output from a sample jsp portlet: Error encountered processing a template: /portlets/html/hello.jsporg.apache.jasper.JasperException: Unable to compile class for JSP at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:561) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:300) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:293) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:286) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:752) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:640) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:552) 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.jetspeed.portal.portlets.viewprocessor.JSPViewProcessor.processView(JSPViewProcessor.java:170) at org.apache.jetspeed.portal.portlets.GenericMVCPortlet.buildContent(GenericMVCPortlet.java:301) at org.apache.jetspeed.portal.portlets.GenericMVCPortlet.getContent(GenericMVCPortlet.java:219) at org.apache.jetspeed.portal.security.portlets.PortletWrapper.getContent(PortletWrapper.java:148) at sun.reflect.GeneratedMethodAccessor194.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:260) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:207) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:250) 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.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.jetspeed.portal.controls.VelocityPortletControl.getContent(VelocityPortletControl.java:170) at sun.reflect.GeneratedMethodAccessor190.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:260) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:207) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:250) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:94) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:344) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:153) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:94) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:344) at
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display [EMAIL PROTECTED] changed: What|Removed |Added Version|5.0.3 |5.0.7 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-08-04 19:24 --- Some progress: Jasper does get invoked in both scenarios through an include (with or without a server restart). However, in the first case, the processed JSP is: /portal/media-type/html/user/turbine/page/default.psml/media-type/html (bad) In the second case, it is: /WEB-INF/templates/jsp/portlets/html/hello.jsp (good) I added a Thread.dumpStack in JspServlet.service, and the stack trace is identical, so I don't understand how it could come from a RD dispatcher bug (which according to the stack trace is the only possible culprit). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display [EMAIL PROTECTED] changed: What|Removed |Added Severity|Blocker |Major Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-08-04 20:22 --- The bug turned out to be a dumb bug in Jasper (after spending one more hour debugging the RD ...). This will be fixed in 5.0.7 (or in the next nightly; applying the patch is trivial if you're using the CVS code). Easy workaround: After editing, you need to click on the home link on the left, or access your portal through a URI which doesn't have a pathInfo. I'm downgrading the severity of the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-08-03 10:32 --- Since the root cause of this can't be identified yet, I'll have to close the report soon as I can't do anything useful with it. Please reopen if you have more information allowing to indentify the root cause of this problem. I have to add that the JSP is only processed by Jasper once Tomcat is restarted (and no dynamic changes have any effect), as the generated source and compiled class for a JSP portlet are only created then. As the logs are empty, I do not believe Jasper is the cause of this problem. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-08-03 17:13 --- This is still a problem which completely prevents someone from using Jetspeed JSP Portlets and Tomcat 5. I have not been able to find even a clue as to why this is happening and the logs have been devoid of any information as to the source of this problem. I've looked at the portal page source and everything about the JSP Portlets is created, title bar, colors, name, except for their JSP content which shows up as a single blank line. Jetspeed JSP Portlets run perfectly under Tomcat 3 and 4 but for some reason not under 5. I did open a Jetspeed bug on the same issue but the Jetspeed team doesn't want to do anything about investigating behavior with Tomcat 5 since it is still alpha. I don't think any of their developers have even installed TC5 yet. As far as the state for this bug, I think it should remain open. The only servlet container that is exhibiting any problem with JSP Portlets is Tomcat 5. Other versions of Tomcat and Resin work just fine. Perhaps some change from the servlet spec has led to the problem. Gerry Reno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-07-01 06:49 --- I don't get the exception on the .war. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-07-01 06:58 --- I can reproduce the behavior, but I don't know if it's caused by an actual Tomcat or Jasper bug. If I stop Tomcat and restart it, I can see the portlets. If I then add a new JSP portlet, none will get displayed (until I restart Tomcat). I recommend you debug this a bit more. I am not interested in Jetspeed, so unless you can point out some bad lower level behavior, I'll eventually close the bug, assuming Jetspeed is doing something wrong at some point. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-07-01 13:15 --- I just tried it (tomcat 5.0.3, JDK 1.4.1_03, Windows 2000, Jetspeed 1.4b4). Dropped jetspeed.war in running tomcat webapps directory. Went to http://localhost:8080/jetspeed, browsed around, everything was fine. Edited a few panes, no problems. Added JSP Portfolio portlet, didn't get an error, but didn't see anything in the portlet (am I supposed to?). Logged out of jetspeed, went to tomcat manager, logged in, reloaded jetspeed webapp. Tried to access http://localhost:8080/jetspeed, got following exception: Horrible Exception: java.lang.Error: Error in BasePeer.initTableSchema (TURBINE_USER): The database is already in use by another process at org.apache.jetspeed.om.security.turbine.BaseTurbineUserPeer.initClass (BaseTurbineUserPeer.java:154) at org.apache.jetspeed.om.security.turbine.BaseTurbineUserPeer. (BaseTurbineUserPeer.java:128) at org.apache.jetspeed.services.security.turbine.TurbineUserManagement.getUser (TurbineUserManagement.java:166) at org.apache.jetspeed.services.JetspeedUserManagement.getUser (JetspeedUserManagement.java:97) at org.apache.jetspeed.services.security.turbine.TurbineAuthentication.getAnonymous User(TurbineAuthentication.java:212) at org.apache.jetspeed.services.JetspeedAuthentication.getAnonymousUser (JetspeedAuthentication.java:102) at org.apache.jetspeed.services.JetspeedSecurity.getAnonymousUser (JetspeedSecurity.java:174) at org.apache.jetspeed.modules.actions.TemplateSessionValidator.doPerform (TemplateSessionValidator.java:97) at org.apache.jetspeed.modules.actions.JetspeedSessionValidator.doPerform (JetspeedSessionValidator.java:103) at org.apache.turbine.modules.Action.perform (Action.java:87) at org.apache.turbine.modules.ActionLoader.exec (ActionLoader.java:122) at org.apache.turbine.Turbine.doGet(Turbine.java:521) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-07-01 13:19 --- Following my post above, I restarted the tomcat server (restarting or reloading the jetspeed application was insufficient), and logged back in. I could see the pane that I added with the same display (i.e. no data) in the JSP stock portfolio portlet. That makes me think it's more likely a Jetspeed issue. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-07-01 13:23 --- Yoav, When you didn't see anything in the JSP Stock Portfolio portlet that is the problem that needs fixed!!! I not inclined one way or the other to say whose issue this is. It could be either a Tomcat or a Jetspeed issue at this point. The behavior doesn't occur in 4.1.24 or Resin so This other exception that you got by reloading jetspeed I have never seen before (on Linux) and I have reloaded jetspeed several times. thx, Gerry Reno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-07-01 13:26 --- I have no idea if it's indeed a Jetspeed bug. I'd like to know if it can be reproduced using something other than Jetspeed (in which case it could indicate a buffering or RD bug). At this point, I don't feel like digging into Jetspeed to get the answer ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-07-01 15:16 --- I also opened a Jetspeed Bugzilla Bug 21232 on this issue and cross-referenced it to this bug. thx, Gerry Reno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-06-30 22:17 --- BTW, I tried this with Tomcat 4.1.24 and the Jetspeed JSP Portlets work fine in that release. thx, Gerry Reno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-06-30 22:18 --- Please investigate this, and point out a TC 5 spec violation causing the wrong behavior. I will close the report if a cause of this behavior cannot be identiied, as it could be an application problem. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-06-30 23:31 --- Remy, Yes, I am not discounting the possibility that this could be some type of app problem. However, the app is working perfectly fine under 4.1.24 and not under 5.0.3. I would think that the specs that relate to rendering of JSP content would be the same as the JSP content in question was JSP 1.2 only - nothing was JSP 2.0. Therefore it seems as though one or the other of the containers is not compliant. The app also appears to work ok under Resin. I am not a spec expert that could pinpoint exactly this problem. Perhaps there is someone else more familiar with the specs and the Tomcat and/or Jetspeed code that could assist here. thx, Gerry Reno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-07-01 00:25 --- I have tried this on win2k. The war file fails. If you expand the .war to directory form, then all is OK. In .war form -- I get a zip exception. So tomcat is OK with respect to running. The unpacking of the war is a different story. For thos curious, here is the part of the stack trace that might look important in case someone might have an immediate a ha!: SEVERE: Exception processing JAR at resource path C:\opt\data\src\TOMCAT5\jakarta-tomcat-5\build\webapps\jetspeed\WEB-INF\lib\jetspeed-1.4-b4.jar in context /jetspeed java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.jar.JarFile.init(JarFile.java:117) at java.util.jar.JarFile.init(JarFile.java:82) at org.apache.catalina.startup.TldConfig.tldScanJar(TldConfig.java:469) at org.apache.catalina.startup.TldConfig.tldScanJar(TldConfig.java:449) at org.apache.catalina.startup.TldConfig.execute(TldConfig.java:228) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4037) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:868) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-07-01 00:38 --- Tim, All of the war files in all of my tests with 5.0.3 and 4.1.24 were fully expanded. What exactly are you saying? Are you seeing the exact same problem? What did you mean when you say 'war file fails'? If you meant you just got a zip exception are you thinking this is related to JSP Portlets not displaying? Gerry Reno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21206] - Tomcat 5 - Jetspeed JSP Portlets do not display
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=21206. 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=21206 Tomcat 5 - Jetspeed JSP Portlets do not display --- Additional Comments From [EMAIL PROTECTED] 2003-07-01 01:36 --- Let me clarify this a little more. Once you have installed the jetspeed.war file go to the jetspeed home page http://localhost:8080/jetspeed . Login as user 'turbine', password 'turbine'. Now, all the default portlets you see on the page are Velocity Portlets. You have to actually add JSP Portlets to the pages before you can even begin to see the problem. Click on the 'Edit HTML' link and select Home then select 'Add Portlet' and from the list of portlets select some of the JSP types such as JSP HelloWorld or JSP Stock Portfolio (on the next page), save and apply your way out and then you should be able to see the problem. thx, Gerry Reno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
