On Wed, 15 Sep 2010 02:45:53 -0300, Stephan Windmüller
<[email protected]> wrote:
On 14.09.2010 18:30, Josh Canfield wrote:
Flash persistence is good for getting data between the action and
render requests. Tapestry does redirect after every event so you'd
generally set the value in an action request so you can use it in the
render request, or vice versa I suppose.
Yes, and with this I have problems since I started using Tapestry.
In a web application written in PHP or JSP for example I can access all
data which is submitted with a form. In Tapestry, it seems not possible.
I guess your problem here is with the redirect-after-post pattern, not
with Tapestry itself. You can access submitted by a form. If some form
field is not bound to a page or component property, you can @Inject
request and use request.getParameter() to get its value.
Between the requests there is no save to the database. I want to user to
be able to add as much values as he wants to the page. All is stored
only if he hits the "save" button at the end.
In this case, you need to use session persistence, not flash persistence.
Flash-persisted properties are removed from the session after they're read
from it.
I am avoiding session persistence because it breaks tabbed browsing. The
user should be able to edit two separate objects in two seperate tabs
simultaneously.
Take a look at
http://docs.codehaus.org/display/TYNAMO/tapestry-conversations+guide.
--
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: [email protected]
For additional commands, e-mail: [email protected]
