Hi Marcel, The GAE sandbox tries to be very lenient with regards to references to classes that aren't on the whitelist. Generally speaking, SecurityExceptions are only thrown if the calling code would have caused the static initializer of the non-whitelisted class to execute. So, for example, just declaring a variable of the type, or even referencing a class-literal of the type, won't cause an exception:
Class<Proxy> klass = Proxy.class; // No exception! On Sun, Aug 1, 2010 at 3:47 PM, Marcel Overdijk <[email protected]>wrote: > I did some further investigations and found out something interesting. > > I used the Java twitter4j library in the past (I'm writing a similar > library for a different service) successfully on app engine. > So I checked the twitter4j source code how they did it and then found > out that the use the Proxy class in their code. > > So I did some test and included the java.net.Proxy class in one of my > test projects on app engine. > Eclipse started complaining about the Proxy not being supported on > GAE, but I deployed in anyway and it worked. > In my case I just had a null value assigned to it but I could > reference java.net.Proxy on the GAE runtime. > > Now I'm just wondering what it means when a class is not on the GAE > Class White List? > > -- > 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 > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- 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 [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-appengine-java?hl=en.
