Hi Alexander
Thanks a lot for the workaround. It is working without any problems.
Hopefully wicket devs will consider making the framework more GAE enabled.
/Murat
On Wed, May 5, 2010 at 9:20 AM, Alexander Monakhov wrote:
> Hey.
>
> I met the same problem when I started to implement my app usin
Hey.
I met the same problem when I started to implement my app using Wicket and
GAE. On GAE there is problem with serialization. GAE prohibits to use
replacement substitution, so WIcket's methods like Component#modelChanged()
or Component#modelChanging() cause AccessControlContext. To fix this pro
Hi All
I am making a small application which is running at appengine. The
code was running fine until i desided to use TabbedPanel.
I have searched on google and it seems like other people have the same
issue. People has reported issues at google appengine,
but cant this not be solved in wicket sc
