You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Lukasz Lenart (Jira)" <ji...@apache.org> on 2020/04/26 05:38:00 UTC
[jira] [Closed] (WW-5030) ClassNotFoundException -
MockPortletResponse
[ https://issues.apache.org/jira/browse/WW-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukasz Lenart closed WW-5030.
-----------------------------
Resolution: Fixed
New plugin with mocks was defined
> ClassNotFoundException - MockPortletResponse
> --------------------------------------------
>
> Key: WW-5030
> URL: https://issues.apache.org/jira/browse/WW-5030
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Portlet
> Affects Versions: 2.5.18
> Reporter: John Bush
> Priority: Major
> Fix For: 2.6
>
> Attachments: TestStrutsPortlet.zip, fail.txt, success.txt
>
>
> WW-3826 solved a problem running JUnit tests on portlet actions that use the struts2-portlet-plugin and struts2-junit-plugin. The solution used Spring's org.springframework.mock.web.portlet package in the spring-test framework. Spring Portlet MVC is no longer supported (SPR-14129) and the package has been removed starting with Spring 5. I'm not able to upgrade to Spring 5 without loosing my unit testing since having both versions of spring-test in my classpath creates many other issues.
> I've attached a zipped portlet project for testing (TestStrutsPortlet.zip), console log from a successful test (success.txt) and console log from a failed test (fail.txt). All that needs to change is the spring-version in the POM to recreate the testing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)