[jira] [Commented] (WICKET-4995) Using CryptoMapper causes page to render twice

["Sven Meier (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734670#comment-13734670 ] 

Sven Meier commented on WICKET-4995:
------------------------------------

WICKET-5309 showed that the url of a page can indeed change after being rendered, when stateful components are added to an otherwise stateless page during rendering (e.g. by repeaters).

Since CryptoMapper changes a url's segments for stateful pages, the page will be re-rendered. To prevent this, call #setStatelessHint(false) on your page.
                
> Using CryptoMapper causes page to render twice
> ----------------------------------------------
>
>                 Key: WICKET-4995
>                 URL: https://issues.apache.org/jira/browse/WICKET-4995
>             Project: Wicket
>          Issue Type: Bug
>            Reporter: Jukka Siivonen
>            Assignee: Sven Meier
>             Fix For: 6.7.0
>
>
> Using Wicket 1.5.9 and CryptoMapper causes our Wicket pages to be rendered twice. I was investigating a problem where a DAO query was executed two times when navigating to a single page.
> In debug call stack I found out that first render is made at  WebPageRenderer.respond(RequestCycle) line: 246	
> and second at WebPageRenderer.respond(RequestCycle) line: 263	
> Removing CryptoMapper from our app configuration fixes the problem.
> It is also possible we are doing something wrong so any help is appreciated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira