Re: ApplicationStates semi bug..

2008-08-12 Thread Fernando Padilla
I was looking over the code, and I saw this: if (!_tracker.getHasErrors()) _tracker.clear(); and should be: if (!_tracker.getHasErrors()) { _tracker.clear(); ValidationTracker tmp = _tracker; _tracker = tmp; } Fernando Padilla wrote: Another nuance I see i

Re: ApplicationStates semi bug..

2008-08-12 Thread Fernando Padilla
Another nuance I see is that a form keeps displaying the old input values.. when normally those are cleared after a form submits. So I'm assuming that the ValidationTracker is not being properly cleared, so maybe some code that clears the validationTracker isn't "setting" it afterwards. that

ApplicationStates semi bug..

2008-08-12 Thread Fernando Padilla
So.. I need confirmation on an HttpSession expected behavior, to see if there is an annoyance with @ApplicationState and @Persist: a) Object value = session.getAttribute( key ); b) value.modifyMe(); c) session.setAttribute( key, value ); It was my understanding (maybe really old servlet spec),