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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
