[
https://issues.apache.org/jira/browse/WICKET-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-3483.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-RC3
Fixed with r1075008.
> NullPointerException in PersistentPageManager's page cache
> ----------------------------------------------------------
>
> Key: WICKET-3483
> URL: https://issues.apache.org/jira/browse/WICKET-3483
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC2
> Environment: Google AppEngine
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Fix For: 1.5-RC3
>
>
> From a private email to me by a user:
> Hi,
> I'm trying to use your gae-initializer to get your test application working
> on GAE. I'm using version 1.5-rc2 of wicket and your initializer. Using GAE
> sdk 1.4.2.
> I'm getting the same problem the person on the 1.5-rc1 release page was
> getting, and I can't get around it.
> The homepage loads, but the other page throws the same null pointer exception
> he was getting:
> java.lang.NullPointerException
> at
> org.apache.wicket.page.PersistentPageManager$SessionEntry.findPage(PersistentPageManager.java:117)
> ....
> --------------------------------
> The problem is that
> org.apache.wicket.page.PersistentPageManager.SessionEntry.addPage(IManageablePage)
> adds even 'null' pages.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
