So, realistically we can expect our users to notice the hick-up at some stage with 5.2.0 (or GWT2.1+ in reality).
Should we consider an emergency game-plan should a fix not be found prior to release? e.g. Remove XSRF protection short-term. It doesn't leave Guvnor any more exposed than we were pre-GWT2.1). I've posted to GWT's forums but had no response as yet.
On 3/23/11 4:34 PM, Michael Anstis wrote:Yes. When first reporting this I was running on JBoss AS 4.2.3.
> Has anybody experienced this in "Web" mode?
rules-dev mailing list