I think we have the same symptoms, and certainly the same error -- we're both getting an ExceptionInInitializerError that only occurs on the server (Hosted-Mode browser and appengine). His doesn't reference JUnit, but I imagine he's just missing a .jar library that's on his eclipse build path, but missing from his WAR -- Java is throwing a class-not-found error with a message related to the PersistenceManager. I think this is just happening because the JDO code eats the actual exception and re-packages it (compounding the problem is that this is actually a JRE initialization error -- it's not really a normal code flow error, so try/catches may not be designed for this use-case).
david On Aug 14, 3:35 pm, Rajeev Dayal <rda...@google.com> wrote: > Hi David, > One more thing - it also seems that your problem was different than Geoff's. > Is that correct? > > Thanks, > Rajeev > --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
