Re: T5: Edit page best practice - Mk III - now Mk V

2008-01-28 Thread Davor Hrg
invalidated form is persisted using @Persist without explicitly defining strategy "session" is default strategy, so yes: if you use the same invalidated form in different windows, expect problems. When "conversation" strategy is implemented this will work just fine :) you can however use @Meta ann

Re: T5: Edit page best practice - Mk III - now Mk V

2008-01-28 Thread Kalle Korhonen
Really important work Geoff, thanks. Which version are you using? I hope you go through the extra work to keep up with the versions. Davor, you say the invalidated form is persisted in session by default. Does multi-window support work in this case, i.e. if the same user opens another edit page fo

Re: T5: Edit page best practice - Mk III - now Mk V

2008-01-28 Thread Davor Hrg
things are a bit different in newer versions, for one, form persists submited data if validation fails, and does not update data on your entity. the invalidated form is persisted default (session if without @Meta) and suits my use fine, I reset form only if new entityid shows up, if you go to: "e

Re: T5: Edit page best practice - Mk III - now Mk V

2008-01-28 Thread Martin Grotzke
Hi Geoff, if validation fails the page is displayed again, and the person will be loaded again in the according GET request - so all input from the user will be lost. We're using flash persistence for this: the person would get annotated with @Persist("flash"), would be reset in cleanupRender and

Re: T5: Edit page best practice - Mk III - now Mk V

2008-01-28 Thread Geoff Callender
Here's Mark V of the single page edit. In previous attempts I was clinging onto client-side persistence of the entity to ensure optimistic locking, and then "the penny finally dropped" - all you need to ensure optimistic locking is to ensure the entity's version is retained - and you can d

Re: T5: Edit page best practice - Mk III - now Mk IV

2007-12-11 Thread Geoff Callender
I'm planning on doing one, but not today. If you know your way around T4 then the web flow example in JumpStart Max 2.0.0 may help you. It's at http://files.doublenegative.com.au/jumpstart/ . Here's Mk IV of the single page edit. It seems that recording errors in onSuccess() can cause fie

Re: T5: Edit page best practice - Mk III

2007-12-11 Thread jeffrey ai
Geoff, I think your code is great for **ONE** edit-page. Our project is looking for a web flow from T5, like the Spring one. Do you have any idea about it? Howard mentioned he may add this feature in the next release. Might be a little late to us, but I am expecting to see it. Cheers, Jeffrey Ai

T5: Edit page best practice - Mk III

2007-12-10 Thread Geoff Callender
Hi, In search of best practice for an "edit" page, here's my 3rd attempt. It's looking pretty clean-cut to me, but I'm looking for suggestions on how to improve it further. private Long _personId; @Persist("client") // Persistence is needed here because this is a