I'm in the process of moving an existing GWt application that uses SQL on the back end over to the AppEngine, and want to do that incrementally. I've found, however, that when I move the source code into an App-Engine project, the system replaces the SecurityManager with one that disallows file access, including the access needed by the MySQL/JDBC adapter. I fully understand why it does that, and want the feature in the long term, but in the short term, it means that I can't compile and run the app unless I eliminate *all *of the database access all at once. I really don't want to make a change of this magnitude in one fell swoop. When I uncheck the "App Engine" box in the Google/AppEngine preferences in Eclipse, Jetti terminates with an exception during the launch process, so that doesn't work as an easy fix.
So, does anybody know an easy way to disable the custom SecurityManager temporarily, short of a kluge, like writing one of my own and replacing the one in the default jar? Lacking that, if you have written a replacement SecurityManger, I'd love to have a copy. Thanks. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-web-toolkit?hl=en.
