You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by david joffrin <da...@hotmail.com> on 2005/04/28 22:45:52 UTC
Reload button causes wierd behavior
Hi,
I have just realized something today on my code, really wierd... I think
this is due to the RequestCycle object, but, I would need some clarification
in order to fix it the right way.
So, the scenario is as follow:
class PageA {
...
onDoSthg(IRequestCycle cycle) {
PageB page = (PageB) cycle.getPage("PageB");
cycle.activate(page);
}
}
After page B is rendered, I click the button RELOAD... then A.onDoSthg is
being re-executed.... Why that?
Thanks.
DvJ
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Reload button causes wierd behavior
Posted by Markus Eberle <ma...@tngtech.com>.
On Friday 29 April 2005 11:53, david joffrin wrote:
> Hi,
>
> Let me summarize all the thread again: EnterOffer page ->
> EnterOfferConfirmation page -> OwnOffer page. All those transitions are done
> through the Submit component and those access methods.
> Sample of the transition EnterOfferConfirmation -> OwnOffer:
> class EnterOfferConfirmation {
> confirmOffer(RequestCycle cycle) {
> OwnOffer ownOffer = (OwnOffer) cycle.getPage("OwnOffer");
> cycle.activate(ownOffer); OR throw new PageRedirectException(ownOffer);
> }
> }
>
> When I click on the reload browser button (AND in both cases, activation or
> redirect exception), my method is executed again entering a new offer in the
> system again (very very bad stuff!).
This you can handle by using some sort of token mechanism, to check whether the
offer was already created.
> How should I then implement it?
> What is the usage of the Submit button if each time I click on reload, the
> previous page is "re-submitted"?
The only way I know to prevent this, is a forward in the HTML (meta-refresh)
as otherwise there is always the trouble that the browser will send the
same information back to the server.
Cheers,
Markus
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Reload button causes wierd behavior
Posted by david joffrin <da...@hotmail.com>.
Hi,
Let me summarize all the thread again: EnterOffer page ->
EnterOfferConfirmation page -> OwnOffer page. All those transitions are done
through the Submit component and those access methods.
Sample of the transition EnterOfferConfirmation -> OwnOffer:
class EnterOfferConfirmation {
confirmOffer(RequestCycle cycle) {
OwnOffer ownOffer = (OwnOffer) cycle.getPage("OwnOffer");
cycle.activate(ownOffer); OR throw new PageRedirectException(ownOffer);
}
}
When I click on the reload browser button (AND in both cases, activation or
redirect exception), my method is executed again entering a new offer in the
system again (very very bad stuff!).
How should I then implement it?
What is the usage of the Submit button if each time I click on reload, the
previous page is "re-submitted"?
Thanks.
David
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Reload button causes wierd behavior
Posted by Markus Eberle <ma...@tngtech.com>.
How is the onDoSthg method invoked? A submit from the browser?
If this is the case, the reload button of the browser resends the last
post request, which was necessary to create the page.
On Friday 29 April 2005 11:35, david joffrin wrote:
> Hi,
>
> Just tried and looked in my debugger... but I go through my method any way!
> Any idea?
>
> Thanks.
> DvJ
>
>
> >From: Andy Pahne <a....@skaffen.de>
> >Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
> >To: Tapestry users <ta...@jakarta.apache.org>
> >Subject: Re: Reload button causes wierd behavior
> >Date: Fri, 29 Apr 2005 08:58:48 +0200
> >
> >
> >class PageA {
> > ...
> > onDoSthg(IRequestCycle cycle) {
> > PageB page = (PageB) cycle.getPage("PageB");
> > throw new PageRedirectException(page);
> > }
> > }
> >
> >
> >
> >
> >
> >
> >david joffrin schrieb:
> > > Hi,
> > >
> > > No, my URL does not indicate anything like direct link, this is a
> > > straight www.mydomain.com/foo/bar.
> > >
> > > Just to test, how can I programmaticly have a redirect rather than an
> > > activation.
> > >
> > > Thanks.
> > > DvJ
> > >
> > >> From: Paul Ferraro <pm...@columbia.edu>
> > >> Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
> > >> To: Tapestry users <ta...@jakarta.apache.org>
> > >> Subject: Re: Reload button causes wierd behavior
> > >> Date: Thu, 28 Apr 2005 16:26:52 -0700
> > >>
> > >> Your url probably indicates a direct link (or similar) that triggers
> > >> the onDoSthg listener of PageA, no? If you find this behavior
> > >> undesirable, then you should redirect to PageB instead of simply
> > >> activating it.
> > >>
> > >> Paul
> > >>
> > >> david joffrin wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> I have just realized something today on my code, really wierd... I
> > >>> think this is due to the RequestCycle object, but, I would need some
> > >>> clarification in order to fix it the right way.
> > >>> So, the scenario is as follow:
> > >>>
> > >>> class PageA {
> > >>> ...
> > >>> onDoSthg(IRequestCycle cycle) {
> > >>> PageB page = (PageB) cycle.getPage("PageB");
> > >>> cycle.activate(page);
> > >>> }
> > >>> }
> > >>>
> > >>> After page B is rendered, I click the button RELOAD... then
> > >>> A.onDoSthg is being re-executed.... Why that?
> > >>>
> > >>> Thanks.
> > >>> DvJ
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Reload button causes wierd behavior
Posted by david joffrin <da...@hotmail.com>.
You can not imagine how much I am grateful for that. I switch to
External_Service as I needed some parameters, but IT IS WORKING.
Thanks again.
DvJ
>From: Paul Ferraro <pm...@columbia.edu>
>Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
>To: Tapestry users <ta...@jakarta.apache.org>
>Subject: Re: Reload button causes wierd behavior
>Date: Fri, 29 Apr 2005 09:44:40 -0700
>
>That's because throwing PageRedirectException simply calls
>cycle.activate(...). To perform a true redirect (so that the page can be
>reloaded without re-executing your listener method), do the following:
>
>IEngineService service =
>cycle.getEngine().getService(Tapestry.PAGE_SERVICE);
>ILink link = service.getLink(cycle, cycle.getPage(), new String[] { "PageB"
>});
>throw new RedirectException(link.getURL());
>
>Paul
>
>david joffrin wrote:
>
>>Hi,
>>
>>Just tried and looked in my debugger... but I go through my method any
>>way! Any idea?
>>
>>Thanks.
>>DvJ
>>
>>
>>>From: Andy Pahne <a....@skaffen.de>
>>>Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
>>>To: Tapestry users <ta...@jakarta.apache.org>
>>>Subject: Re: Reload button causes wierd behavior
>>>Date: Fri, 29 Apr 2005 08:58:48 +0200
>>>
>>>
>>>class PageA {
>>> ...
>>> onDoSthg(IRequestCycle cycle) {
>>> PageB page = (PageB) cycle.getPage("PageB");
>>> throw new PageRedirectException(page);
>>> }
>>> }
>>>
>>>
>>>
>>>
>>>
>>>
>>>david joffrin schrieb:
>>> > Hi,
>>> >
>>> > No, my URL does not indicate anything like direct link, this is a
>>> > straight www.mydomain.com/foo/bar.
>>> >
>>> > Just to test, how can I programmaticly have a redirect rather than an
>>> > activation.
>>> >
>>> > Thanks.
>>> > DvJ
>>> >
>>> >> From: Paul Ferraro <pm...@columbia.edu>
>>> >> Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
>>> >> To: Tapestry users <ta...@jakarta.apache.org>
>>> >> Subject: Re: Reload button causes wierd behavior
>>> >> Date: Thu, 28 Apr 2005 16:26:52 -0700
>>> >>
>>> >> Your url probably indicates a direct link (or similar) that triggers
>>> >> the onDoSthg listener of PageA, no? If you find this behavior
>>> >> undesirable, then you should redirect to PageB instead of simply
>>> >> activating it.
>>> >>
>>> >> Paul
>>> >>
>>> >> david joffrin wrote:
>>> >>
>>> >>> Hi,
>>> >>>
>>> >>> I have just realized something today on my code, really wierd... I
>>> >>> think this is due to the RequestCycle object, but, I would need some
>>> >>> clarification in order to fix it the right way.
>>> >>> So, the scenario is as follow:
>>> >>>
>>> >>> class PageA {
>>> >>> ...
>>> >>> onDoSthg(IRequestCycle cycle) {
>>> >>> PageB page = (PageB) cycle.getPage("PageB");
>>> >>> cycle.activate(page);
>>> >>> }
>>> >>> }
>>> >>>
>>> >>> After page B is rendered, I click the button RELOAD... then
>>> >>> A.onDoSthg is being re-executed.... Why that?
>>> >>>
>>> >>> Thanks.
>>> >>> DvJ
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>>---------------------------------------------------------------------
>>> >>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> >>> For additional commands, e-mail:
>>>tapestry-user-help@jakarta.apache.org
>>> >>>
>>> >>
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> >> For additional commands, e-mail:
>>>tapestry-user-help@jakarta.apache.org
>>> >>
>>> >
>>> >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>> >
>>> >
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Reload button causes wierd behavior
Posted by Paul Ferraro <pm...@columbia.edu>.
That's because throwing PageRedirectException simply calls
cycle.activate(...). To perform a true redirect (so that the page can
be reloaded without re-executing your listener method), do the following:
IEngineService service =
cycle.getEngine().getService(Tapestry.PAGE_SERVICE);
ILink link = service.getLink(cycle, cycle.getPage(), new String[] {
"PageB" });
throw new RedirectException(link.getURL());
Paul
david joffrin wrote:
> Hi,
>
> Just tried and looked in my debugger... but I go through my method any
> way! Any idea?
>
> Thanks.
> DvJ
>
>
>> From: Andy Pahne <a....@skaffen.de>
>> Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
>> To: Tapestry users <ta...@jakarta.apache.org>
>> Subject: Re: Reload button causes wierd behavior
>> Date: Fri, 29 Apr 2005 08:58:48 +0200
>>
>>
>> class PageA {
>> ...
>> onDoSthg(IRequestCycle cycle) {
>> PageB page = (PageB) cycle.getPage("PageB");
>> throw new PageRedirectException(page);
>> }
>> }
>>
>>
>>
>>
>>
>>
>> david joffrin schrieb:
>> > Hi,
>> >
>> > No, my URL does not indicate anything like direct link, this is a
>> > straight www.mydomain.com/foo/bar.
>> >
>> > Just to test, how can I programmaticly have a redirect rather than an
>> > activation.
>> >
>> > Thanks.
>> > DvJ
>> >
>> >> From: Paul Ferraro <pm...@columbia.edu>
>> >> Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
>> >> To: Tapestry users <ta...@jakarta.apache.org>
>> >> Subject: Re: Reload button causes wierd behavior
>> >> Date: Thu, 28 Apr 2005 16:26:52 -0700
>> >>
>> >> Your url probably indicates a direct link (or similar) that triggers
>> >> the onDoSthg listener of PageA, no? If you find this behavior
>> >> undesirable, then you should redirect to PageB instead of simply
>> >> activating it.
>> >>
>> >> Paul
>> >>
>> >> david joffrin wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> I have just realized something today on my code, really wierd... I
>> >>> think this is due to the RequestCycle object, but, I would need some
>> >>> clarification in order to fix it the right way.
>> >>> So, the scenario is as follow:
>> >>>
>> >>> class PageA {
>> >>> ...
>> >>> onDoSthg(IRequestCycle cycle) {
>> >>> PageB page = (PageB) cycle.getPage("PageB");
>> >>> cycle.activate(page);
>> >>> }
>> >>> }
>> >>>
>> >>> After page B is rendered, I click the button RELOAD... then
>> >>> A.onDoSthg is being re-executed.... Why that?
>> >>>
>> >>> Thanks.
>> >>> DvJ
>> >>>
>> >>>
>> >>>
>> >>>
>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> >>> For additional commands, e-mail:
>> tapestry-user-help@jakarta.apache.org
>> >>>
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail:
>> tapestry-user-help@jakarta.apache.org
>> >>
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Reload button causes wierd behavior
Posted by david joffrin <da...@hotmail.com>.
Hi,
Just tried and looked in my debugger... but I go through my method any way!
Any idea?
Thanks.
DvJ
>From: Andy Pahne <a....@skaffen.de>
>Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
>To: Tapestry users <ta...@jakarta.apache.org>
>Subject: Re: Reload button causes wierd behavior
>Date: Fri, 29 Apr 2005 08:58:48 +0200
>
>
>class PageA {
> ...
> onDoSthg(IRequestCycle cycle) {
> PageB page = (PageB) cycle.getPage("PageB");
> throw new PageRedirectException(page);
> }
> }
>
>
>
>
>
>
>david joffrin schrieb:
> > Hi,
> >
> > No, my URL does not indicate anything like direct link, this is a
> > straight www.mydomain.com/foo/bar.
> >
> > Just to test, how can I programmaticly have a redirect rather than an
> > activation.
> >
> > Thanks.
> > DvJ
> >
> >> From: Paul Ferraro <pm...@columbia.edu>
> >> Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
> >> To: Tapestry users <ta...@jakarta.apache.org>
> >> Subject: Re: Reload button causes wierd behavior
> >> Date: Thu, 28 Apr 2005 16:26:52 -0700
> >>
> >> Your url probably indicates a direct link (or similar) that triggers
> >> the onDoSthg listener of PageA, no? If you find this behavior
> >> undesirable, then you should redirect to PageB instead of simply
> >> activating it.
> >>
> >> Paul
> >>
> >> david joffrin wrote:
> >>
> >>> Hi,
> >>>
> >>> I have just realized something today on my code, really wierd... I
> >>> think this is due to the RequestCycle object, but, I would need some
> >>> clarification in order to fix it the right way.
> >>> So, the scenario is as follow:
> >>>
> >>> class PageA {
> >>> ...
> >>> onDoSthg(IRequestCycle cycle) {
> >>> PageB page = (PageB) cycle.getPage("PageB");
> >>> cycle.activate(page);
> >>> }
> >>> }
> >>>
> >>> After page B is rendered, I click the button RELOAD... then
> >>> A.onDoSthg is being re-executed.... Why that?
> >>>
> >>> Thanks.
> >>> DvJ
> >>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> >>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Reload button causes wierd behavior
Posted by Andy Pahne <a....@skaffen.de>.
class PageA {
...
onDoSthg(IRequestCycle cycle) {
PageB page = (PageB) cycle.getPage("PageB");
throw new PageRedirectException(page);
}
}
david joffrin schrieb:
> Hi,
>
> No, my URL does not indicate anything like direct link, this is a
> straight www.mydomain.com/foo/bar.
>
> Just to test, how can I programmaticly have a redirect rather than an
> activation.
>
> Thanks.
> DvJ
>
>> From: Paul Ferraro <pm...@columbia.edu>
>> Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
>> To: Tapestry users <ta...@jakarta.apache.org>
>> Subject: Re: Reload button causes wierd behavior
>> Date: Thu, 28 Apr 2005 16:26:52 -0700
>>
>> Your url probably indicates a direct link (or similar) that triggers
>> the onDoSthg listener of PageA, no? If you find this behavior
>> undesirable, then you should redirect to PageB instead of simply
>> activating it.
>>
>> Paul
>>
>> david joffrin wrote:
>>
>>> Hi,
>>>
>>> I have just realized something today on my code, really wierd... I
>>> think this is due to the RequestCycle object, but, I would need some
>>> clarification in order to fix it the right way.
>>> So, the scenario is as follow:
>>>
>>> class PageA {
>>> ...
>>> onDoSthg(IRequestCycle cycle) {
>>> PageB page = (PageB) cycle.getPage("PageB");
>>> cycle.activate(page);
>>> }
>>> }
>>>
>>> After page B is rendered, I click the button RELOAD... then
>>> A.onDoSthg is being re-executed.... Why that?
>>>
>>> Thanks.
>>> DvJ
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Reload button causes wierd behavior
Posted by david joffrin <da...@hotmail.com>.
Hi,
No, my URL does not indicate anything like direct link, this is a straight
www.mydomain.com/foo/bar.
Just to test, how can I programmaticly have a redirect rather than an
activation.
Thanks.
DvJ
>From: Paul Ferraro <pm...@columbia.edu>
>Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
>To: Tapestry users <ta...@jakarta.apache.org>
>Subject: Re: Reload button causes wierd behavior
>Date: Thu, 28 Apr 2005 16:26:52 -0700
>
>Your url probably indicates a direct link (or similar) that triggers the
>onDoSthg listener of PageA, no? If you find this behavior undesirable,
>then you should redirect to PageB instead of simply activating it.
>
>Paul
>
>david joffrin wrote:
>
>>Hi,
>>
>>I have just realized something today on my code, really wierd... I think
>>this is due to the RequestCycle object, but, I would need some
>>clarification in order to fix it the right way.
>>So, the scenario is as follow:
>>
>>class PageA {
>>...
>>onDoSthg(IRequestCycle cycle) {
>> PageB page = (PageB) cycle.getPage("PageB");
>> cycle.activate(page);
>>}
>>}
>>
>>After page B is rendered, I click the button RELOAD... then A.onDoSthg is
>>being re-executed.... Why that?
>>
>>Thanks.
>>DvJ
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Reload button causes wierd behavior
Posted by Paul Ferraro <pm...@columbia.edu>.
Your url probably indicates a direct link (or similar) that triggers the
onDoSthg listener of PageA, no? If you find this behavior undesirable,
then you should redirect to PageB instead of simply activating it.
Paul
david joffrin wrote:
> Hi,
>
> I have just realized something today on my code, really wierd... I
> think this is due to the RequestCycle object, but, I would need some
> clarification in order to fix it the right way.
> So, the scenario is as follow:
>
> class PageA {
> ...
> onDoSthg(IRequestCycle cycle) {
> PageB page = (PageB) cycle.getPage("PageB");
> cycle.activate(page);
> }
> }
>
> After page B is rendered, I click the button RELOAD... then A.onDoSthg
> is being re-executed.... Why that?
>
> Thanks.
> DvJ
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org