struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From René Gielen (Jira) <>
Subject [jira] [Commented] (WW-5030) ClassNotFoundException - MockPortletResponse
Date Tue, 25 Feb 2020 11:10:00 GMT


René Gielen commented on WW-5030:

It might be considerable to contact the current maintainers before forking. You could argue
it is a friendly notice, while not specifically required. Moreover, it might be worth to check
whether extracting out a "portlet-test-support" library does make sense, preferrably with
the help of the current maintainers.

Speaking of that, I don't think the Spring folks would be the right ones to talk to, since
the project was handed over to Liferay. IMO if we see value in talking, they would be the
right address.

> ClassNotFoundException - MockPortletResponse
> --------------------------------------------
>                 Key: WW-5030
>                 URL:
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - Portlet
>    Affects Versions: 2.5.18
>            Reporter: John Bush
>            Priority: Major
>             Fix For: 2.6
>         Attachments:, 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 (, 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

View raw message