Hi, 1 of the reasons is that all applications don't run all at the same version on the gae productive infrastructure. So, google would have to know which one you are using in order to put it for you in your war when you upload it. It's probably simpler to handle if the developper puts the jars at the correct level in his war by himself (1 less database to manage / update / etc...) for Google.
It then most probably provide a more resilient infrastructure. There are probably other reasons. regards didier On May 9, 12:03 am, arjan tijms <[email protected]> wrote: > Hello Guys, > > I've searched this group and didn't find the answer for the following > question. > > Why should I bring appengine-api.jar with me to the GAE server? Isn't > this weird? Creating a new Google "Web Application Project" in Eclipse > automatically puts this jars and some 10 others in the WEB-INF/lib > directory of my project. When I remove them, the google appengine > validator produces warnings: > > Google App Engine Problem (10 items) > The App Engine SDK JAR appengine-api-1.0-sdk-1.4.3.jar is missing > in the WEB-INF/lib directory > > I mean it is not so hard to bring that jar with application, but it > reduces my application startup time and it makes it hard to > distinguish the jars I added myself and those which the project adds > by default. And as I mentioned, it's just plain weird. The server is > supposed to have the implementations of the classes in those jars > already. Why on earth should they be bundled in my war??? -- 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.
