[Trinidad] Can't see any difference when setting stateSaving=client on the tr:document element

Hi ! As I recently reported in a old thread ([Trinidad] Nightly Builds?), I eventually took the time to deploy the official 1.2.14 build of Trinidad in order to try the fix for TRINIDAD-1772 (Allow per page state saving settings) https://issues.apache.org/jira/browse/TRINIDAD-1772, but I don't

Re: [Trinidad] Nightly Builds?

Hi ! I eventually took the time to deploy the official 1.2.14 build of Trinidad in order to try the fix for TRINIDAD-1772 (Allow per page state saving settings) https://issues.apache.org/jira/browse/TRINIDAD-1772, but I don't see any change in the result... I have added stateSaving=client on the

Re: [Trinidad] Nightly Builds?

Hi guys ! I've been monitoring JIRA for the 1.2.14 target for a while, waiting to be able to use page-specific states (TRINIDAD-1772 :  Allow per page state saving settings) in order to avoid ViewExpiredExceptions on our login dialog for instance, and it looks like the 1.2.14 release has

Re: [Trinidad] Nightly Builds?

Hi guys ! Can't see anything built today. Any idea when 1.2.14 will be released? Yes please ! I've been monitoring JIRA for the 1.2.14 targethttps://issues.apache.org/jira/browse/TRINIDAD/fixforversion/12314551for a while, waiting to be able to use page-specific states ( TRINIDAD-1772

Re: Server side error messages need to be cleared when resubmitted the page to prevent duplicate display

Hi ! We also faced this issue, and the quickest / less dirty way we found to address it was to write a small Java Script method, that gets called on all form submissions using onsubmit : tr:form id=smc_domain_form onsubmit=SMCClearAllMsg();return true; This method first removes the