So as suspected this is a consequence of wicket7 upgrade. The generated id preserves the state of the page and prevents the "double submit problem" to occur.
The feature can be turned off with a simple setting to make it clustering compatible. However that will imply that refreshing a page will cause it to loose its status and that users may be confronted with the double submit problem. I see three possible solutions: 1. turn it off for everyone 2. allow the clustering plug-ins to turn it off programmatically 3. make it fully user configurable What is the preferred choice? Cheers Niels On 29-04-16 14:19, Niels Charlier wrote: > On 28-04-16 02:48, Jody Garnett wrote: >> And we should report this to Jira :( >> > https://osgeo-org.atlassian.net/browse/GEOS-7526 > > I am working on reproducing the issue. > > Regards > Niels > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications Manager > Applications Manager provides deep performance insights into multiple tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
