Thank you, the pointer to 1.2.5 was incorrect in Eclipse as you suggested, and now all my massive number of compiler errors are gone (thank god, and thank you again).
What's curious is that I'm still using String and Exception and other java.lang classes, and they work fine on the engine too, yet I've not read anything in the documentation (yet) that indicates java.lang.* is unsupported. How is this possible? How can it be Java without supporting java.lang.*, which certainly seems to be doing? On Sep 22, 5:46 pm, Toby Reyelts <[email protected]> wrote: > App Engine no longer supports classes from java.lang.*. You can work around > this by bundling your own versions of java.lang.String and > java.lang.Exception with your webapp. > > Seriously though, please check that your Eclipse project is pointing to a > valid 1.2.5 App Engine SDK installation. There is a known issue with the > Eclipse IDE where it can sometimes too aggressively remove plugins which it > believes are no longer in use. > > > > On Tue, Sep 22, 2009 at 5:20 PM, Eric Atkinson <[email protected]> wrote: > > > I justed updated to App Engine 1.2.5 and now all my software is full > > of compiler errors because it says app engine no longer support > > classes like String, Exception, SAXParser in Java. Should I revert > > back to an earlier app engine that did support them or is this really > > the "new" app engine support? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
