as able to fix this by
getting the collection size prior to persisting the object in page 1 to the
session state. Seems like a bit of a hack to me. Thanks Guys.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Building-object-through-wizard-tp5713417p5713422.html
Sent fr
Thanks Guys, for your input. All very helpful.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Building-object-through-wizard-tp5713417p5713420.html
Sent from the Tapestry - User mailing list archive at Nabble.com
On Fri, 25 May 2012 11:02:42 -0300, George Christman
wrote:
miserably with that. "Maybe I'm missing something". So my question is
therea alternative solution such as SessionState or Persist where I
could store the object in memory and then later save?
Why not SessionState? Unless you nee
as a way to persist it
>> with hibernate and retrieve it on the next page, but I've failed
>> miserably with that. "Maybe I'm missing something". So my
>> question is there a alternative solution such as SessionState or
>> Persist where I could store the ob
sing something". So my question is there
> a alternative solution such as SessionState or Persist where I could store
> the object in memory and then later save?
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Building-object-through-wizard-tp
ersist where I could store
the object in memory and then later save?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Building-object-through-wizard-tp5713417.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
--
