Hi,
At the beginning - hello everyone, I'm new here. And - starting with
question. Probably it was already here many times, so please point me
the URL to the archivized message so we don't spam the group:)
My question is directed rather to Howard himself - why do we need
rewinding in Tapestry? Well, I've read this part of "Tapestry in
Action", so it's not "please explain me what it is". Just wondering - why?
This causes so many Stale Exceptions. As for me, it conflicts with
the idea of components design. A simple example - three components, one
for displaying item, second for adding subitems, third for displaying
subitems. Everything in one form, put one by one. What happens if I add
new subitem? You know the answer. Well, I can easily solve it as
everyone suggests everywhere, by performing actions in form submit,
after it's all rewinded... But the huge problems appears if a Page has
the form, and subcomponents are form elements (well, maybe it's such a
special case?) and due to our components-design we want to split the
actions.
What is the most unclear to me - ... Howard mentions he was basing on
WebObjects. I'm 2 years now using WebObjects, and there things simply
work! Of course I don't blame Howard - he did a great job with Tapestry!
But my question is - what caused the problems he couldn't jump over with
such a basic fields? This Stale exceptions, using special Conditionals
in Forms? I don't get it (yet)...
--
Greets!
Adam Czysciak
[EMAIL PROTECTED]
Sun Certified Programmer for the Java 2 Platform, SE 5.0
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
