Is it possible to remove this binding between Google AppEngine, Jetty, and GWT.... and re-link the project back to tomcat ( such as the older method before the eclipse plugin ) ? Besides having major memory issues within hosted mode, the application is no longer functional due to a java socket policy issue which occurs somewhere between the AppEngine loading the jdbc class, Jetty handling the remote request, and GWT. I've tried just about everything to fix this problem, and have pin-pointed the solution down to either adding the security policy to the runtime securitymanager for jetty/appengine, or having the jar resource available during hosted mode runtime for either AppEngine or Jetty ( which seems to be a setting within the jdoconfig, or some other area for the appengine ). Google's jdoconfig docs is limited for what I am searching for. I'm just... lost.
Any assistance is greatly appreciated. Regards, Jonathan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
