Hi Lukasz, Thanks for your answer. Yes, it seems related, adding this constant works around the issue. Out of curiosity, is the problem the conversion from List to XWorkList mentioned by Yasser <https://issues.apache.org/jira/browse/WW-4954?focusedCommentId=16593382&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16593382> ?
Follow up questions: 1. What is the expected impact of this change? On our previous upgrade from 34 to 35 our risk assessment determined no risk, based on the assumption that the change was backwards compatible. Since it is not (and we need to perform the additional change in struts.xml), can you tell us if there is any area we should worry about when upgrading? 2. Should the logs have shown this? With devMode=true, I see no difference in the logs from 34 to 35 3. Is it possible to change the release notes to tell about this incompatibility? Going forward, is there a way to improve the compatibility assessments? Kind regards, Miguel On Thu, Aug 30, 2018 at 7:21 AM Lukasz Lenart <lukaszlen...@apache.org> wrote: > śr., 29 sie 2018 o 19:04 Miguel Almeida <migueldealme...@gmail.com> > napisał(a): > > *And *scopesValues was previously set (<s:set var="scopeValues" > > value="scopes"></s:set>, where scopes is a List<String>scopes in the > action) > > It is probably related to this issue > > https://issues.apache.org/jira/browse/WW-4954?focusedCommentId=16593403&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16593403 > > You can temporary use the posted workaround but we will fix that in > incoming two minor releases. > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > >
