[
https://issues.apache.org/jira/browse/WICKET-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eelco Hillenius resolved WICKET-202.
------------------------------------
Resolution: Fixed
> pageExpiredErrors with wicket pages in jsp-includes
> ----------------------------------------------------
>
> Key: WICKET-202
> URL: https://issues.apache.org/jira/browse/WICKET-202
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-quickstart
> Affects Versions: 1.2.2
> Environment: windows.
> Reporter: Wolfgang Gehner
> Priority: Critical
> Attachments: wicket-quickstart.zip
>
>
> Hi there, we want to integrate Wicket with other rendering
> technologies. One example is including wicket pages in a jsp.
> Attached is the use case as an Eclipse project based on Wicket trunk of today.
> Run the application as usual with Start - run as java application,
> then go to http://localhost:8081/quickstart/index.jsp
> Two problems:
> 1. Upon first entry on index.jsp, clicking "Open Dialog" and closing
> redirects to App Main page, console shows "INFO -
> uestTargetResolverStrategy - component not enabled or visible,
> redirecting to calling page, component: null"
> 2. Incrementing values on [Wicket Page2] and opening and closing
> Dialog on [Wicket Page1] *sometimes* results in PageExpired Error,
> usually after some wait.
> I wonder what to do to stabilize this. We hope we can make Wicket
> coexist with other technologies such as JSP. After all, everything is
> just servlets :-)
> Regards,
> Wolfgang
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
