This seems like a complicated solution, and I don't quite understand the reason the problem existed with the previous solution. Was there a way the projectGroupSummary page could be restructured so that this wasn't an issue?
- Brett On 15/04/2011, at 8:01 PM, [email protected] wrote: > Author: oching > Date: Fri Apr 15 10:01:18 2011 > New Revision: 1092648 > > URL: http://svn.apache.org/viewvc?rev=1092648&view=rev > Log: > [CONTINUUM-2622] > o do an explicit check for a random generated value in the action on remove > project group (built-in token session interceptor doesn't work for > projectGroupSummary page because > the <s:action> tag (which executes result) for getting the projects in the > group in the page causes a double submit > o enabled selenium test for remove project group csrf check -- Brett Porter [email protected] http://brettporter.wordpress.com/
