[
https://issues.apache.org/struts/browse/WW-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nils-Helge Garli resolved WW-2977.
----------------------------------
Resolution: Not A Problem
Assignee: Nils-Helge Garli
The portlet example app is supposed to be deployed in a portlet container. The
statup actions are specified in the portlet.xml file.
> STruts portlet has no startup jsp
> ---------------------------------
>
> Key: WW-2977
> URL: https://issues.apache.org/struts/browse/WW-2977
> Project: Struts 2
> Issue Type: Bug
> Components: Example Applications
> Affects Versions: 2.1.6
> Environment: TC 6 JDK 6 4GB ram 1/2 tera diskspace
> Reporter: Martin Gainty
> Assignee: Nils-Helge Garli
>
> struts2-portlet.war has no index.jsp
> does not have default jsp in web,xml
> If i decide to add a index.jsp I configure in the edit/index.jsp
> <welcome-file-list>
> <welcome-file>./WEB-INF/edit/index.jsp</welcome-file>
> </welcome-file-list>
> which produces this display
> type Exception report
> message
> description The server encountered an internal error () that prevented it
> from fulfilling this request.
> exception
> org.apache.jasper.JasperException: The Struts dispatcher cannot be found.
> This is usually caused by using Struts tags without the associated filter.
> Struts tags are only usable when the request has passed through its servlet
> filter, which initializes the Struts dispatcher needed for this tag. -
> [unknown location]
>
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:522)
>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:416)
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> root cause
> The Struts dispatcher cannot be found. This is usually caused by using
> Struts tags without the associated filter. Struts tags are only usable when
> the request has passed through its servlet filter, which initializes the
> Struts dispatcher needed for this tag. - [unknown location]
> org.apache.struts2.views.jsp.TagUtils.getStack(TagUtils.java:60)
>
> org.apache.struts2.views.jsp.StrutsBodyTagSupport.getStack(StrutsBodyTagSupport.java:44)
>
> org.apache.struts2.views.jsp.ComponentTagSupport.doStartTag(ComponentTagSupport.java:48)
>
> org.apache.jsp.WEB_002dINF.edit.index_jsp._jspx_meth_s_005furl_005f0(index_jsp.java:108)
> org.apache.jsp.WEB_002dINF.edit.index_jsp._jspService(index_jsp.java:68)
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> note The full stack trace of the root cause is available in the Apache
> Tomcat/6.0.18 logs.
> I'll try to place org.apache.struts2.portlet.dispatcher.DispatcherServlet on
> CLASSPATH
> Here is the configuration for DispatcherServlet from web.xml
> <servlet id="Struts2PortletDispatcherServlet">
> <servlet-name>Struts2PortletDispatcherServlet</servlet-name>
>
> <servlet-class>org.apache.struts2.portlet.dispatcher.DispatcherServlet</servlet-class>
> </servlet>
> neatly packaged in /WEB-INF/lib/70,223 struts2-portlet-plugin-2.1.6.jar
> ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
