you can build it pretty easy.
Just extend WebSession and hold a map with pages you like to pool.
Christian Essl wrote:
I was just following the discussion on the Tapestry and JSF comparision.
I wonder if it is possible to use in wicket pooled pages. Something
like a detachable-model for
Thanks for the answers. And you are right it is no good idea and does not
work. This seems just to be one of the arguments which is often used for
Tapestry (Session efficency).
Christian
On Fri, 26 Aug 2005 15:28:38 +0200, Eelco Hillenius
[EMAIL PROTECTED] wrote:
No! A page is a specific
don't use static ofcourse, but we all know that ;)
Eelco Hillenius wrote:
No! A page is a specific instance of one user. What would you accomplish?
Eelco
On 8/26/05, Johan Compagner [EMAIL PROTECTED] wrote:
you can build it pretty easy.
Just extend WebSession and hold a map with pages you
Thanks,
Sorry if I expressed myself unclear, but I rather meant to share the same
page-instance for different users (not concurrently). But it does not work
and was a rather stupid question.
Christian
On Fri, 26 Aug 2005 15:21:45 +0200, Johan Compagner [EMAIL PROTECTED]
wrote:
you can
I was just following the discussion on the Tapestry and JSF comparision.
I wonder if it is possible to use in wicket pooled pages. Something like a
detachable-model for pages which gets stored in the Session instead of the
actual page. Can something similar be achieved in wicket?
I don't
ahh
ok now i get also eelco's response
many people are asking the question but then mean for one session (how
to reuse pages)
But no storing them in such a thing as an application wouldn't be very
wise i think.
But what is really gained? Memory? If you use detachable models i don't
Pooling has some huge drawbacks since it really goes against the
language itself. I think it's good for things like DB connections that
really are expensive, but for pages? They're just objects.
On 8/26/05, Johan Compagner [EMAIL PROTECTED] wrote:
ahh
ok now i get also eelco's response
I just read a few chapters of Bitter EJB. A large part of the book is
about how to avoid state. Allthough stateless session beans were not
designed to be that important, they now play a central role in J2EE.
The consequence is that large parts of the J2EE community got back to
procedural
