https://github.com/martin-g/wicket-gae-demo/commit/617561afc2b38e36884d59c9076342dec889d13d

<https://github.com/martin-g/wicket-gae-demo/commit/617561afc2b38e36884d59c9076342dec889d13d>Happy
wicketing in Google AppEngine ;-)

On Sat, Nov 13, 2010 at 12:15 PM, Ernesto Reinaldo Barreiro <
[email protected]> wrote:

> Martin,
>
> That´s why new HttpSessionStore was needed. There was a post some
> weeks ago  about a Mencache  based session store that might be usefull
> for GAE application  but I never got to try it.
>
> Cheers,
>
> Ernesto
>
>
> On Sat, Nov 13, 2010 at 11:06 AM, Martin Grigorov <[email protected]>
> wrote:
> > Hi Ernesto,
> >
> > As far as you don't try to store a page (i.e. serialize it to byte[])
> > everything is OK.
> >
> > If anyone wants to experiment:
> > https://github.com/martin-g/wicket-gae-demo
> >
> > touch pom.xml to point to the folder where you have appengine sdk.
> >
> > @Rodolfo Hansen: thanks for the maven plugin ;-)
> >
> > martin-g
> >
> > On Sat, Nov 13, 2010 at 9:28 AM, Ernesto Reinaldo Barreiro <
> > [email protected]> wrote:
> >
> >> Martin,
> >>
> >> AFAIK you need:
> >>
> >> 1- getResourceSettings().setResourcePollFrequency(null);
> >>
> >> 2- Use HTTP session store.
> >>       @Override
> >>        protected ISessionStore newSessionStore()
> >>        {
> >>                // for Google App Engine
> >>                return new HttpSessionStore(this);
> >>        }
> >>
> >> at least for 1.4.X.
> >>
> >> Regards,
> >>
> >> Ernesto
> >>
> >>
> >> On Fri, Nov 12, 2010 at 5:30 PM, Martin Grigorov <[email protected]>
> >> wrote:
> >> > Hi GAE users,
> >> >
> >> > I'm trying to run Wicket 1.5 application in Google AppEngine and I'm
> >> > experiencing problem for which I cannot find a solution so far:
> >> >
> >> > SEVERE: Error serializing object class org.wicketstuff.gae.HomePage
> >> > [object=[Page class = org.wicketstuff.gae.HomePage, id = 0, render
> count
> >> =
> >> > 1]]
> >> > java.security.AccessControlException: access denied
> >> > (java.io.SerializablePermission enableSubclassImplementation)
> >> > at
> >> >
> >>
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:323)
> >> > at
> >>
> java.security.AccessController.checkPermission(AccessController.java:546)
> >> > at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> >> > at
> >> >
> >>
> com.google.appengine.tools.development.DevAppServerFactory$CustomSecurityManager.checkPermission(DevAppServerFactory.java:166)
> >> > at java.io.ObjectOutputStream.<init>(ObjectOutputStream.java:253)
> >> > at
> >> >
> >>
> org.apache.wicket.util.io.WicketObjectOutputStream.<init>(WicketObjectOutputStream.java:437)
> >> > at
> >> >
> >>
> org.apache.wicket.util.io.WicketObjectStreamFactory.newObjectOutputStream(WicketObjectStreamFactory.java:49)
> >> > at
> >> >
> >>
> org.apache.wicket.util.lang.WicketObjects.objectToByteArray(WicketObjects.java:475)
> >> > at
> >> >
> >>
> org.apache.wicket.pageStore.DefaultPageStore.serializePage(DefaultPageStore.java:364)
> >> > at
> >> >
> >>
> org.apache.wicket.pageStore.DefaultPageStore.storePage(DefaultPageStore.java:153)
> >> > ....
> >> >
> >> > The problem is described at
> >> > http://code.google.com/p/googleappengine/issues/detail?id=2500
> >> >
> >> > Basically GAE doesn't allow "new ObjectOutputStream()" which is
> necessary
> >> to
> >> > convert Page object to byte[].
> >> > I tried:
> >> > - both IObjectStreamFactories - DefaultOSF and WicketOSF
> >> > - added <sessions-enabled>true</sessions-enabled> in appengine-web.xml
> >> > - add
> >> > <system-properties>
> >> > <property name="com.google.appengine.runtime.environment"
> >> value="Production"
> >> > />
> >> > </system-properties>
> >> >
> >> > What I miss to be able to run Wicket app in GAE ?
> >> > I know there are some users of Wicket 1.4 out there - please advice!
> >> >
> >> > martin-g
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to