[
https://issues.apache.org/jira/browse/WW-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213666#comment-13213666
]
Bruce Phillips edited comment on WW-3763 at 2/22/12 2:49 PM:
-------------------------------------------------------------
This "feature" of Struts and the Struts portlet plugin is just something we
took advantage of and is one reason we continue to use Struts 2. At our
university we have a portal (JASIG's uPortal). For some of our applications we
need a portlet to run inside the portal and a version of the application that
runs as a separate web application for people who cannot login to our Portal.
Deploying the single war file created by the project would deploy the portlet
and the separate web application. This gave us the advantage of a single
project to create both the portlet and standalone web application.
With the previous versions of the Struts portlet plugin we could configure two
different packages in struts XML. One that extended struts-default and one
that extended struts-portlet-default. The packages would have actions for both
the standalone web application and for the portlet. Previously the portlet
plugin did not interfere with the actions that were in the package that
extended struts-default. With the upgrade to version 2.3.1.2 it now appears
that the plugin does interfere with calling/executing actions defined in the
package that extended struts-default.
If this "feature" is no longer available with Struts portlet plugin version
2.3.1.2 then before upgrading we will need to rework a few projects to separate
out the web application and the portlet application. We would like to upgrade
to 2.3.1.2 due to the improved security of that version.
If this "feature" can be restored in the next Struts version of the portlet
plugin, we can wait for that before upgrading.
So we just need to know if this is an issue that will be fixed in the next
release or if from now on we need to completely separate our portlet and web
applications.
Thank you for the help.
was (Author: phillips1021):
This "feature" of Struts and the Struts portlet plugin is just something we
took advantage of and is one reason we continue to use Struts 2. At our
university we have a portal (JASIG's uPortal). For some of our applications we
need a portlet to run inside the portal and a version of the application that
runs as a separate web application for people who cannot login to our Portal.
Deploying the single war file created by the project would deploy the portlet
and the separate web application. This gave use the advantage of a single
project to create both the portlet and standalone web application.
With the previous versions of the Struts portlet plugin we could configure two
different packages in struts XML. One that extended struts-default and one
that extended struts-portlet-default. The packages would have actions for both
the standalone web application and for the portlet. Previously the portlet
plugin did not interfere with the actions that were in the package that
extended struts-default. With the upgrade to version 2.3.1.2 it now appears
that the plugin does interfere with calling/executing actions defined in the
package that extended struts-default.
If this "feature" is no longer available with Struts portlet plugin version
2.3.1.2 then before upgrading we will need to rework a few projects to separate
out the web application and the portlet application. We would like to upgrade
to 2.3.1.2 due to the improved security of that version.
If this "feature" can be restored in the next Struts version of the portlet
plugin, we can wait for that before upgrading.
So we just need to know if this is an issue that will be fixed in the next
release or if from now on we need to completely separate our portlet and web
applications.
Thank you for the help.
> Struts Portlet Plugin Version 2.3.1.2 Breaks Using Struts Project For Both
> Portlet and Standalone Application
> -------------------------------------------------------------------------------------------------------------
>
> Key: WW-3763
> URL: https://issues.apache.org/jira/browse/WW-3763
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Portlet
> Affects Versions: 2.3.1.2
> Environment: Java JDK 6, Tomcat 6
> Reporter: Bruce Phillips
>
> I've got a few Struts application where I use the Struts 2 portlet plugin to
> create a portlet and still have a standalone web application.
> This worked fine through Struts 2 portlet plugin version 2.2.1.1. For an
> example of this problem download and unzip this Eclipse/Maven project:
>
> http://code.google.com/p/struts2-examples/downloads/detail?name=Struts2CRUDPortletExample_Finish.zip
> (read the README.txt file for how to build/deploy).
> This project uses Struts 2.2.1.1. It builds a war file that when deployed to
> Tomcat will register a portlet (that can be used in the Pluto portal
> container) and a web application that can be accessed via calls to Struts
> Actions.
> I tried to upgrade this project to use Struts version 2.3.1.2 (both core and
> portlet plugin). The port let still works fine. But after upgrading to
> 2.3.1.2 when trying to load an action for the standalone version (an action
> defined in package extends="struts-default") I get the following exception:
> Struts Problem Report
> Struts has detected an unhandled exception:
> Messages:
> java.lang.reflect.InvocationTargetException
> java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> An exception occurred processing JSP page /jsp/employees.jsp at line 5 2:
> <%@ taglib prefix="s" uri="/struts-tags" %> 3: 4: 5: 6: 7: 8: Stacktrace:
> File: org/apache/struts2/portlet/context/PortletActionContext.java
> Line number: 225
> Stacktraces
> org.apache.jasper.JasperException: An exception occurred processing JSP page
> /jsp/employees.jsp at line 5 2: <%@ taglib prefix="s" uri="/struts-tags" %>
> 3: 4: 5: 6: 7: 8: Stacktrace:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
