On Sat, 26 Feb 2011 11:28:31 -0300, Adam Zimowski <zimowsk...@gmail.com>
wrote:
Is it possible to have a grid with one form for each row?
I don't think so. In this case, can you use Loop instead?
For the errors outside Form part: I've never tried that, but Form has a
tracker parameter. It's type is ValidationTracker (implemented by
ValidationTrackerImpl, which is not internal), which is the interface that
stores the error mesages. You could pass your own instance of
ValidationTracker, maybe stored as a @Persist("flash") field of your page
or component.
I'm making a progress on my project with Tapestry, which is to rewrite
a working Struts website without a single UI change. Great framework
for the basics, but from what I have experienced so far, the learning
curve to override and customize seemingly simple things is just
astronomical. The framework is great at getting things done quickly
with defaults, but the minute you want to override some behavior
Tapestry seems to be very rigid.
Could you describe what simple things had "astronomical" effort to be
done? This would be a very interesting feedback.
Sometimes, in this list, we see people having difficulties for trying
implement something using a given component or service in a way that it
was never meant to be used. See this:
http://tapestry.1045711.n5.nabble.com/Problem-with-BeanEditForm-validation-td2845764.html#a2845836
"BeanEditForm is a scaffolding component; although it is quite
configurable and extensible, if you have very involved and specific client
requirements for layout and validation, just use a normal Form and related
components."
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
