On Tue, 20 May 2014 10:50:08 -0300, Stephen Nutbrown <steves...@gmail.com>
wrote:
Hello,
Hi!
Thank you again Thiago, Thilo and Java Lance over on StackOverflow - I
posted a link there to this mailing list thread so anyone can follow
if they come searching for the same issue.
Adding formState="interation" did the trick, the Result object was
already persisted.
Yay!
I have learnt a few things from this:
1- Putting things in components is generally very strongly advised. I
have around 10 at the moment, but there are certainly a lot of things
which I should move in to components to make the project easier to
manage. It is rather likely that at some stage soon I will be
re-factoring my whole project (which is rather large, consisting of 59
classes (10 components, 18 pages, 9 entities, several "utility"
classes and some services). I finally have some time to be working on
this project rather than being pulled in lots of directions, so now
is the time (It has suffered from lots of "cheapo" solutions this last
few months).
I suggest Tapestry-IoC services to replace the utility classes. You get a
lot more flexibility with just some few minor changes.
2- I now know what formState="interaction" is. Following the advice I
looked it up here:
http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/corelib/LoopFormState.html
3- I owe the community a great deal of thanks :)
Thank you! You have made my day.
Nice! :D
I've just posted my answer in StackOverflow too. :)
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
