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=6689>. 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=6689 Tomcat can not load action servlet (missing message resource) Summary: Tomcat can not load action servlet (missing message resource) Product: Struts Version: Nightly Build Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Blocker Priority: Other Component: Controller AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] All of the currently-available daily builds appear to be broken -- at least as far as Forte 3.0 and its internal Tomcat server is concerned. None of the example Struts applications from recent (2/18, 2/22, and 2/25) daily builds work under Forte's internal Tomcat server. I listed the bug as "Blocker" because currently, the only way to get the logic:messagesPresent tag is to use the daily build, but a sampling of the daily builds currently available for download (only the last 2 weeks' worth) suggests that they're all unusable. Perhaps it might be a good idea to pick one of the more stable nightly builds from December or January and classify it as a milestone release, precisely to avoid this situation (all currently available nightly builds broken) in the future? ;-) This specific example below came from struts-blank's index.jsp from the 2/18 daily build, but I got more or less the same result from struts-example and struts-exercise-taglib from both the 2/22 and 2/25 daily builds as well. Tomcat reports "cannot load servlet name: action" in its error output window The Browser displays: Error: 500 Location: /index.jsp Internal Servlet Error: javax.servlet.ServletException: Cannot find message resources under key org.apache.struts.action.MESSAGE at org.apache.jasper.runtime.PageContextImpl.handlePageException (PageContextImpl.java:459) at _0002findex_0002ejspindex_jsp_0._jspService (_0002findex_0002ejspindex_jsp_0.java:251) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service (JspServlet.java:177) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:318) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391) at org.netbeans.modules.web.tomcat.JspServlet.service (JspServlet.java:91) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService (ServletWrapper.java:404) at org.apache.tomcat.core.Handler.service(Handler.java:286) at org.apache.tomcat.core.ServletWrapper.service (ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService (ContextManager.java:797) at org.apache.tomcat.core.ContextManager.service (ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection (HttpConnectionHandler.java:210) at org.apache.tomcat.service.TcpWorkerThread.runIt (PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run (ThreadPool.java:498) at java.lang.Thread.run(Thread.java:536) Root cause: javax.servlet.jsp.JspException: Cannot find message resources under key org.apache.struts.action.MESSAGE at org.apache.struts.util.RequestUtils.message(RequestUtils.java:735) at org.apache.struts.taglib.bean.MessageTag.doStartTag (MessageTag.java:295) at _0002findex_0002ejspindex_jsp_0._jspService (_0002findex_0002ejspindex_jsp_0.java:97) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service (JspServlet.java:177) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:318) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391) at org.netbeans.modules.web.tomcat.JspServlet.service (JspServlet.java:91) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService (ServletWrapper.java:404) at org.apache.tomcat.core.Handler.service(Handler.java:286) at org.apache.tomcat.core.ServletWrapper.service (ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService (ContextManager.java:797) at org.apache.tomcat.core.ContextManager.service (ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection (HttpConnectionHandler.java:210) at org.apache.tomcat.service.TcpWorkerThread.runIt (PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run (ThreadPool.java:498) at java.lang.Thread.run(Thread.java:536) How to replicate: Use WinZip to extract any of the sample application .war files into a directory. Launch Forte (v3, with all current bugfixes and jdk1.4 release) Create a new project mount the directory into which the .war file was extracted as a filesystem Go to the "project" tab, right-click, and choose "build project" Get food. It'll take a few minutes. ;-) right-click "index"(.jsp) and choose "Execute (Force Reload)" -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
