[appengine-java] Re: AccessControlException (SerializablePermission enableSubclassImplementation) - Wicket on GAE
Hi there: We've been running a wicket app on gae since last month, but without the need of implement memcache-based implementation of Wicket's IPageStore. Why are you doing that? (our wicket version is 1.3.7) Regards, Esteban a.maza escribió: > Hi, > > I am trying to get Apache Wicket running properly on GAE. Therefore, I > am adapting some Wicket behavior (i.e., I am trying to implement a > Memcache-based implementation of Wicket's IPageStore). > > Anyway, I am getting a > > java.security.AccessControlException: access denied > (java.io.SerializablePermission enableSubclassImplementation) > > error when running my code on the dev server. It seems to me that the > use of java.io.ObjectOutputStream causes some problems although the > class is found on the JRE whitelist. > > Below you find the (shortened) stacktrace: > > > java.security.AccessControlException: access denied > (java.io.SerializablePermission enableSubclassImplementation) > at java.security.AccessControlContext.checkPermission(Unknown Source) > at java.security.AccessController.checkPermission(Unknown Source) > at java.lang.SecurityManager.checkPermission(Unknown Source) > at com.google.appengine.tools.development.DevAppServerFactory > $CustomSecurityManager.checkPermission(DevAppServerFactory.java:139) > at java.io.ObjectOutputStream.(Unknown Source) > at org.apache.wicket.util.io.IObjectStreamFactory > $DefaultObjectStreamFactory$2.(IObjectStreamFactory.java:150) > at org.apache.wicket.util.io.IObjectStreamFactory > $DefaultObjectStreamFactory.newObjectOutputStream > (IObjectStreamFactory.java:114) > at org.apache.wicket.util.lang.Objects.objectToByteArray(Objects.java: > ) > at > org.apache.wicket.protocol.http.pagestore.AbstractPageStore.serializePage > (AbstractPageStore.java:203) > > > > Any help would be highly appreciated ;-) > > thanks, > andr > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: AccessControlException (SerializablePermission enableSubclassImplementation) - Wicket on GAE
On 21 Okt., 20:26, Esteban Masoero wrote: > Hi there: > > We've been running a wicket app on gae since last month, but without the > need of implement memcache-based implementation of Wicket's IPageStore. > Why are you doing that? (our wicket version is 1.3.7) Wicket is very powerful in maintaining application/session state. This enables for example a nice usage of back/forward buttons. In a typical scenario, this is backed by the DiskPageStore implementation. On GAE you can't use the DiskPageStore since it relies on writing to the filesystem. Thus, I assume that you use the HTTPSessionStore as proposed in some blog entries (and not the SecondLevelCacheStore). I did some research on the web and several users reported problems using the HTTPSessionStore - especially regarding the back/forward button behavior. Thus, I am currently trying to implement a Memcache- backed IPagestore for GAE. On the Wicket mailinglist I was provided with a HTTP session based implementation of IPageStore (done in the Terracotta project) to have a starting point (http://www.nabble.com/ Google-App-Engine-and-Wicket-to23001592.html) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: AccessControlException (SerializablePermission enableSubclassImplementation) - Wicket on GAE
a.maza: That's correct, I'm using HTTPSessionStore because of the filesystem writing restriction. However, I'm interested in the implementation you are trying to do, so if you decide to share it with the community when it's done, I'll be happy to give it a try ;). Moreover, we have a fileupload gae-like implementation that uses the datastore instead of the file system to store temporary recently uploaded files (shared by a developer in the wicket users list), so I'd be interested in merging our code and your code into some wicket-gae.jar extension, so everything its located at one place and can be reused by others. For the record, we haven't experienced any issues related to the back/foward button behavior (although I must tell that our app is still a small one and maybe that has something to do with it). Regards, Esteban a.maza escribió: > > On 21 Okt., 20:26, Esteban Masoero wrote: > >> Hi there: >> >> We've been running a wicket app on gae since last month, but without the >> need of implement memcache-based implementation of Wicket's IPageStore. >> Why are you doing that? (our wicket version is 1.3.7) >> > > Wicket is very powerful in maintaining application/session state. This > enables for example a nice usage of back/forward buttons. In a typical > scenario, this is backed by the DiskPageStore implementation. On GAE > you can't use the DiskPageStore since it relies on writing to the > filesystem. Thus, I assume that you use the HTTPSessionStore as > proposed in some blog entries (and not the SecondLevelCacheStore). > > I did some research on the web and several users reported problems > using the HTTPSessionStore - especially regarding the back/forward > button behavior. Thus, I am currently trying to implement a Memcache- > backed IPagestore for GAE. On the Wicket mailinglist I was provided > with a HTTP session based implementation of IPageStore (done in the > Terracotta project) to have a starting point (http://www.nabble.com/ > Google-App-Engine-and-Wicket-to23001592.html) > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: AccessControlException (SerializablePermission enableSubclassImplementation) - Wicket on GAE
I'll be happy to share the code as soon as it is running smoothly and I got rid of the above mentioned AccessControlException. Thus, I hope somebody could give me a hint what is causing the exception. Regards, andr On 21 Okt., 23:14, Esteban Masoero wrote: > a.maza: > > That's correct, I'm using HTTPSessionStore because of the filesystem > writing restriction. However, I'm interested in the implementation you > are trying to do, so if you decide to share it with the community when > it's done, I'll be happy to give it a try ;). Moreover, we have a > fileupload gae-like implementation that uses the datastore instead of > the file system to store temporary recently uploaded files (shared by a > developer in the wicket users list), so I'd be interested in merging our > code and your code into some wicket-gae.jar extension, so everything its > located at one place and can be reused by others. > > For the record, we haven't experienced any issues related to the > back/foward button behavior (although I must tell that our app is still > a small one and maybe that has something to do with it). > > Regards, > > Esteban > > a.maza escribió: > > > > > > > On 21 Okt., 20:26, Esteban Masoero wrote: > > >> Hi there: > > >> We've been running a wicket app on gae since last month, but without the > >> need of implement memcache-based implementation of Wicket's IPageStore. > >> Why are you doing that? (our wicket version is 1.3.7) > > > Wicket is very powerful in maintaining application/session state. This > > enables for example a nice usage of back/forward buttons. In a typical > > scenario, this is backed by the DiskPageStore implementation. On GAE > > you can't use the DiskPageStore since it relies on writing to the > > filesystem. Thus, I assume that you use the HTTPSessionStore as > > proposed in some blog entries (and not the SecondLevelCacheStore). > > > I did some research on the web and several users reported problems > > using the HTTPSessionStore - especially regarding the back/forward > > button behavior. Thus, I am currently trying to implement a Memcache- > > backed IPagestore for GAE. On the Wicket mailinglist I was provided > > with a HTTP session based implementation of IPageStore (done in the > > Terracotta project) to have a starting point (http://www.nabble.com/ > > Google-App-Engine-and-Wicket-to23001592.html)- Zitierten Text ausblenden - > > - Zitierten Text anzeigen - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: AccessControlException (SerializablePermission enableSubclassImplementation) - Wicket on GAE
I've created an issue for it... http://code.google.com/p/googleappengine/issues/detail?id=2334 On 22 Okt., 08:52, "a.maza" wrote: > I'll be happy to share the code as soon as it is running smoothly and > I got rid of the above mentionedAccessControlException. > > Thus, I hope somebody could give me a hint what is causing the > exception. > > Regards, > andr > > On 21 Okt., 23:14, Esteban Masoero wrote: > > > > > a.maza: > > > That's correct, I'm using HTTPSessionStore because of the filesystem > > writing restriction. However, I'm interested in the implementation you > > are trying to do, so if you decide to share it with the community when > > it's done, I'll be happy to give it a try ;). Moreover, we have a > > fileupload gae-like implementation that uses the datastore instead of > > the file system to store temporary recently uploaded files (shared by a > > developer in the wicket users list), so I'd be interested in merging our > > code and your code into some wicket-gae.jar extension, so everything its > > located at one place and can be reused by others. > > > For the record, we haven't experienced any issues related to the > > back/foward button behavior (although I must tell that our app is still > > a small one and maybe that has something to do with it). > > > Regards, > > > Esteban > > > a.maza escribió: > > > > On 21 Okt., 20:26, Esteban Masoero wrote: > > > >> Hi there: > > > >> We've been running a wicket app on gae since last month, but without the > > >> need of implement memcache-based implementation of Wicket's IPageStore. > > >> Why are you doing that? (our wicket version is 1.3.7) > > > > Wicket is very powerful in maintaining application/session state. This > > > enables for example a nice usage of back/forward buttons. In a typical > > > scenario, this is backed by the DiskPageStore implementation. On GAE > > > you can't use the DiskPageStore since it relies on writing to the > > > filesystem. Thus, I assume that you use the HTTPSessionStore as > > > proposed in some blog entries (and not the SecondLevelCacheStore). > > > > I did some research on the web and several users reported problems > > > using the HTTPSessionStore - especially regarding the back/forward > > > button behavior. Thus, I am currently trying to implement a Memcache- > > > backed IPagestore for GAE. On the Wicket mailinglist I was provided > > > with a HTTP session based implementation of IPageStore (done in the > > > Terracotta project) to have a starting point (http://www.nabble.com/ > > > Google-App-Engine-and-Wicket-to23001592.html)- Zitierten Text ausblenden - > > > - Zitierten Text anzeigen -- Zitierten Text ausblenden - > > - Zitierten Text anzeigen - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
