A couple of other people in the group have resolved this issue by JARing up their custom classes, rather than loading them up from the WEB-INF/classes.
You'll notice that all of your errors come from class resolution or classpath scanning - it seems the file system on GAE is particularly slow, so by loading the classes from a single resource you can get much more consistent load times. The more frameworks you use with classpath scanning, the more the filesystem impacts your load times. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/O4UYHrLgB9wJ. 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.
