I tried to resurrect a thread to ask questions regarding
ValidationDecorator and Bean Validation integration but now I think that was
not the best approach, so I decided to start a new thead.
I'm trying to write a custom ValidationDecorator that must meet the
following requirements:
- Re
Right, the trick is calling discardPersistentFieldChanges() at the
right time. You cannot, or at least it doesn't make sense in the
general case, to simply call it on browser's onunload().
Tapestry-conversations module relies on the idea of short term
expiration of page-specific session data, where
discardPersistentFieldChanges() will discard @Persist values, but the
original question was how to do it when the user leaves the page.
Read Howard's message here along with the following messages:
http://markmail.org/message/67dbxuwf3rw3naja
In a nutshell, it was easy to implement pageReset, but
Hi!
Sorry about resurrecting this thread but a have a similar requirement
(render a decoration (eg an '*') in front of labels of every required field)
and some problems.
I'd like to render the decoration with the same style as the label when
the field is in error. My custom ValidationDec
thank you
I still have no time for the migration but it's necessary
2010/12/23
> I have convected my 5.0 app to 5.2. The major problem was the
> BeanValidator and that was something I should have spotted right away.
> Most of the work was replacing the deprecated items. All of these I
> repl
On Mon, 27 Dec 2010 10:38:08 -0200, Duruk_Kab
wrote:
I have used the same JavaScript + CSS code for synchronization purpose,
the main problem with this is, we are facing many perfomance issues.
Most probably it's in the database. Turning the log level so low as you
did hurts performance
Thanks for the help.
I have used the same JavaScript + CSS code for synchronization purpose, the
main problem with this is, we are facing many perfomance issues.
I have put SOPs to figure out which part of code is taking huge time and
found out that, it is tapestry which is taking most part of t
It's called discardPersistentFieldChanges:
http://tapestry.1045711.n5.nabble.com/T5-Cleaning-page-s-persistent-field-td2419355.html
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/T5-2-4-How-to-discard-persistent-fields-when-the-user-leaves-a-page-tp5867260p5869215.html
Hi everyone,
I am using an AjaxFormLoop in a page. However, after I load the page with
the AjaxFormLoop and a few minutes have passed, when I click the "Add row"
link I get the following exception and a new row is not added. However, if I
click it again, then no exception is shown and a new row is
I have opened a new post since I get a different error with the AjaxFormLoop
different from TAP5-733.
Thanks again
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/AjaxFormLoop-in-Tapestry-5-1-0-8-SNAPSHOT-tp3303062p3319221.html
Sent from the Tapestry - User mailing list a
10 matches
Mail list logo