To conclude my discussion with myself. After re-installing a new eclipse and fresh plugin the final answer here is that the error actually looks like it was caused by an old version of jdom. Replacing it with the jdom1.1 jar is what solved the problem. No idea why GAE doesn't like old jdom but there it is.
On Mar 4, 1:36 pm, bgood <[email protected]> wrote: > It looks like the problem for both errors was that I had a dependent > class from jdom.jar that was not included when I deployed the app. My > bad, bizarre though. It was there on my classpath in eclipse, was > there in my WEB-INF/LIB folder and the application worked fine > locally. The only clue in Eclipse was that the jar file was not > visible in WEB-INF/LIB when I looked - though it was there when I > looked directly at the file system. Dropping a new jdom.jar into the > lib folder (and saying 'yes I do want to replace the old one') appears > to have solved the problem. > > So, I guess nothing wrong with the gae, but some weirdness happening > in my eclipse plugin/installation. > > On Mar 4, 11:48 am, bgood <[email protected]> wrote: > > > > > I just reuploaded an app that I is working locally (and has been > > working fine live for a while) and I'm getting two different security > > related errors in different areas of the app. > > > java.lang.SecurityException: Unable to get members for class ... > > and > > java.lang.SecurityException: SHA1 digest error for org/jdom/ > > Content.class > > > Is anyone having a similar problem today? > > Any ideas where to look to debug? -- 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.
