[ http://issues.apache.org/jira/browse/WICKET-69?page=all ]
Gustavo Hexsel updated WICKET-69:
---------------------------------
Attachment: tester.zip
The example is based on the wicket-portlet-examples project, I just simplified
the pages and duplicated the code (to put 2 portlets in the page), being
careful not to have reused wicket:ids.
This was written to run on Liferay, but there's nothing container-specific that
I can point at.
> Wicket Portlets don't support multiple porlets in a single app
> --------------------------------------------------------------
>
> Key: WICKET-69
> URL: http://issues.apache.org/jira/browse/WICKET-69
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.2.4
> Environment: Ubuntu Linux 6.10, Liferay+Tomcat 5.5.17 (single bundle)
> From my limited understanding, should affect other environments as well.
> Reporter: Gustavo Hexsel
> Attachments: tester.zip
>
>
> Creating a single app with multiple portlets seems to lead to
> PageExpiredException when both portlets submit data in the same Session (I'm
> submitting them one after the other - nothing fancy, just the same Session).
> When I submit a form on one, then after a refresh submit the other, I get 3
> rendering phases, 2 of them for the portlet that was last clicked.
> I've attached an example. I've removed the lib folder to make the size
> manageable - will need commons-logging, log4j and some snapshot of Wicket
> Core.
> It all works as long as you don't submit both forms in the same
> session, then the second one always fails by displaying a "Portlet expired"
> or similar message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
