On May 13, 2:29 am, Nichole <[email protected]> wrote: > Just a quick summary, the servlet spec requires that a servlet > container such as appengine > provider an implementation for a service. Those jars such as servlet- > api-2.4.jar are needed > at compile time.
That's why there's provided scope in Maven. > They are sometimes provided by the servlet container/ > engines at run time > in a global directory that is found by the container/engine > classloader. They have to always be provided by the container. E.g. the HttpServletRequest interface that the container classes implement and that you program against have to be the same class defined by the same classloader otherwise you get a LinkageError. > appengine provides > the servlet, jsp implementations for us at runtime. > > The appengine specific service implementations are also needed at > runtime and compile > time and are present in the appengine-api-1.0-sdk-<ver>.jar. > They've chosen not to add the latest sdk to the container global > classpath, so yes, the > application must provide it. But that's silly. That means you deploy the local simulation implementations into production. Cheers Philipe -- 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.
