Em Tue, 07 Oct 2008 18:23:05 -0300, John Jimmy Dondapati
<[EMAIL PROTECTED]> escreveu:
Here are the options with T5 (from what we could dig up) :
2. Pass on the Request object between the Pages using
Page1.java
Object onSubmitFromForm()
{
nextPage.setRequestObject(this.requestObject());
return nextPage;
}
In this case, you wouldn't use the page activation context, as you're
filling the page properties yourself. As Tapestry uses redirect-after-post
by default (and not using it can lead to several problems), you would need
to @Persist("flash") the property in all pages. The single giant ASO would
be a better fit instead of this.
It looks like I cannot pass my custom Classes (requestObjects) this way.
Are only the built-in datatype classes allowed for OnActivate() and
OnPassivate() e.g. String or Long ?
You can use String[] and List as well.
We dont know if any of these would work for us coz we are looking at min
10k concurrent users for this form wizard when it goes up. Are we
missing some other approach. Please advise. Thanks!
Could you use the middle ground solution of storing a temporary object in
a database at each page, reloading it at each page and only storing the
object in the right table in the end of the wizard? You trade database
communication and processing for per-user memory consumption.
In any case, huge forms are always a pain and I try to avoid them as much
as I can.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
Consultor, desenvolvedor e instrutor em Java
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
