So, realistically we can expect our users to notice the hick-up at some stage with 5.2.0 (or GWT2.1+ in reality).<br><br>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.<br>
<br>Views anybody?<br><br>Cheers,<br><br>Mike<br><br><div class="gmail_quote">On 24 March 2011 14:26, Tihomir Surdilovic <span dir="ltr"><<a href="mailto:tsurdilo@redhat.com">tsurdilo@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On 3/23/11 4:34 PM, Michael Anstis wrote:<br>
> Has anybody experienced this in "Web" mode?<br>
</div>Yes. When first reporting this I was running on JBoss AS 4.2.3.<br>
<br>
Thanks.<br>
_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</blockquote></div><br>