2009/4/14 Yogurt Earl <[email protected]> > > Has anyone tried guice-servlet (http://code.google.com/p/google-guice/ > wiki/Servlets <http://code.google.com/p/google-guice/%0Awiki/Servlets>) or > warp-servlet (www.wideplay.com/warp::servlet )? >
yes, I've tried a custom build of guice + guice-servlet and it appears to work ok ( I patched guice with the latest google-collections code which supports GAE ) my specific patches are available here: http://peaberry.googlecode.com/svn/tags/1.1/lib/build/UPDATE_COLLECTIONS_20090412.txt http://peaberry.googlecode.com/svn/tags/1.1/lib/build/GUICE_ISSUE_343_SRC_20090304.txt the resulting Guice jar (r929+patches) is available in the latest release of peaberry: http://peaberry.googlecode.com/files/peaberry-1.1.zip this zipfile doesn't contain guice-servlet - but you can either grab that from a recent snapshot of Guice, or you could build it yourself from trunk (note the above patches don't affect guice-servlet, only the core Guice code) HTH - happy hacking ;) On Apr 9, 1:41 am, Scott Hernandez <[email protected]> wrote: > > Once I added a try/catch SecurityException to Finalizer.java > > everything now runs on GAE. > > > > I'm not sure what the consequences are of removing the Finalizer > > thread, but let's call that google's problem! > > > > Finalizer.java:81 > > try{ > > Finalizer finalizer = new > Finalizer(finalizableReferenceClass, > > frq); > > finalizer.start(); > > return finalizer.queue; > > }catch (SecurityException se){ > > //GAE -- security blows! > > } > > return null; > > > > On Apr 9, 12:54 am, Scott Hernandez <[email protected]> wrote: > > > > > Which is the next error I get if I work against trunk. Of course, this > > > all works in the dev-env cause it doesn't have the same security > > > policy! > > > > > java.security.AccessControlException: access denied > > > (java.lang.RuntimePermission modifyThreadGroup) > > > at java.security.AccessControlContext.checkPermission(Unknown > Source) > > > at java.security.AccessController.checkPermission(Unknown > Source) > > > at java.lang.SecurityManager.checkPermission(Unknown Source) > > > at > com.google.apphosting.utils.security.SecurityManagerInstaller > > > $CustomSecurityManager.checkAccess(SecurityManagerInstaller.java:72) > > > at java.lang.ThreadGroup.checkAccess(Unknown Source) > > > at java.lang.Thread.init(Unknown Source) > > > at java.lang.Thread.<init>(Unknown Source) > > > at > com.google.inject.internal.Finalizer.<init>(Finalizer.java:92) > > > at > com.google.inject.internal.Finalizer.startFinalizer(Finalizer.java: > > > 81) > > > ... > > > > > I'm taking a look at the static Finalizer code now. But considering I > > > don't have any experience with this, I'm not sure how much of a hack I > > > can make... > > > > > On Apr 9, 12:09 am, Stuart McCulloch <[email protected]> wrote: > > > > > > 2009/4/9 Scott Hernandez <[email protected]> > > > > [snip] > > > > yes the Google App Engine has a strict security manager - it also > doesn't > > > > allow you to create threads > > > > > > btw, this exception should be fixed in trunk ( > http://code.google.com/p/google-guice/issues/detail?id=336) > > > -- Cheers, Stuart --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-guice?hl=en -~----------~----~----~----~------~----~------~--~---
