Eelco Hillenius wrote:
>
>> Lets say that we wanted to do "sophisticated clustering", so we use the
>> ONE_PASS_RENDER option. However, we still want to avoid the double-submit
>> problem. Is it possible? Is there a way the application can prevent it
>> from
>> happening in this case?
>
> Sure
Eelco Hillenius wrote:
>
> On Nov 18, 2007 2:55 AM, mfs <[EMAIL PROTECTED]> wrote:
>>
>> Yeah that scenario still makes sense where the user goes to the form page
>> itself, but i was refering to the scenario where the user goes to the
>> page
>> (with the back button) which got shown after form
void oninitialsubmit();
> protected abstract void onresubmit();
>
> protected final void onsubmitted() {
> if (!submitted) oninitialsubmit(); else onresubmit();
> submitted=true;
> }
> }
>
> why does wicket need a special mechanism?
>
>
> On Nov 19, 2007 6:57
I agree -- I had a question about this very topic. I was going to ask:
Does Wicket have any mechanism to notify the application that a form from a
previous page has been re-submitted (the situation you describe below)?
This is so that the application can decide what to do -- in some cases, the
b
> On Fri, 16 Nov 2007, saenz wrote:
>> In fact, I can't tell whether the IPageMap or the IPageVersionManager (or
>> both) are used to serialize old versions of Page instances. I would
>> assume
>> that IPageVersionManager is where this is implemented, but I can'
and other
experts can provide is greatly appreciated.
- Lu
Martijn Dashorst wrote:
>
> How can he be more specific than give you the method you need to override?
> Martijn
>
> On Nov 17, 2007 12:53 AM, saenz <[EMAIL PROTECTED]> wrote:
>
>>
>> Hi Johan,
>>
&g
Johan Compagner wrote:
>
> what do you mean with disabled? how is it disabled?
> The page can't be serialized because of none serializeable attributes?
> Then in the default 1.3 configuration that page can't be saved to disk so
> you can't restore it.
>
Hi Johan,
What I mean is by using the t
Hi Johan,
Would you mind being a little bit more specific? Or you may feel free to
point me to the documentation that I should read.
Johan Compagner wrote:
>
> Application
> *protected* *abstract* ISessionStore newSessionStore();
>
--
View this message in context:
http://www.nabble.com/Di
Also, can someone answer this other question I asked?
saenz wrote:
>
>> Also -- if page serialization is disabled, what happens when the user
>> hits
>> the back button?
>
--
View this message in context:
http://www.nabble.com/Disabling-serialization-storage-of-pag
igor.vaynberg wrote:
>
> you can still cluster 1.3.1 easily. either use httpsessionstore or
> tell wicket to save pages to a shared drive
>
Thanks Igor. Are you saying that we can configure Wicket to store old
versions of Pages in the HttpSessionStore (in memory)? If so, how do we
configure t
By the way, my question below still has not been answered. Can anyone explain
what would occur in the following scenario?
> My question regarding on-disk page storage relates to the use case of a
> web-app deployed on a cluster. In this situation, what will happen if the
> following occurs?
>
Johan Compagner wrote:
>
> On Nov 15, 2007 11:22 PM, Eelco Hillenius <[EMAIL PROTECTED]>
> wrote:
>> Recommended is to use sticky sessions.
>
> +1
>
> none sticky sessions are flawed anyway.. (or the synchronizing performance
> hit is so great it doesn't make any sense, it it makes sense t
igor.vaynberg wrote:
>
> you will get an error, i have explained this in a parallel thread
> yesterday... that is why we are working on a special page store that
> will also write out the current page onto the disk when the session is
> replicated - that means all nodes will have all the pages s
Martijn Dashorst wrote:
>
> failover?
>
> On 11/16/07, saenz <[EMAIL PROTECTED]> wrote:
>>
>>
>> Johan Compagner wrote:
>> >
>> > On Nov 15, 2007 11:22 PM, Eelco Hillenius <[EMAIL PROTECTED]>
>> > wrote:
>> >> Recommend
Eelco Hillenius wrote:
>
>> If need be, can we disable altogether the storage of pages (in the form
>> of a
>> pageMap) in session, similarly on the disk ?
>
> Yep. One easy way to achieve this is to provide a dummy page store.
>
My question regarding on-disk page storage relates to the use c
Johan Compagner wrote:
>
> The DiskStore is for the backbutton and the PageMap (thats in the session)
> is for the current page. And as long as that page is statefull you have to
> store it in the session.
>
What is the lifetime of a Page object stored in the session?
Does Wicket manage the l
16 matches
Mail list logo
