The plot thickens. I just uploaded another version of my app with similar code, including the offending MappingUtils class. This version has no troubles with it. This means that the MappingUtils class is not really the problem - there is something specific to the version that is manifesting a SecurityException but the true problem is not described in that exception.
If you are a kind-hearted Google engineer, my problematic version is "integrate-1-0-0" I'm using the fact that versions in Appengine can run different code but share the same database. This is great for separating code out for different purposes (and reducing the classes loaded for threads since they don't need everything) but it seems that there's a classloader price to be paid here. Help! -- 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-j...@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.
