Google App Engine
Apache Wink is run using Google App Engine as the core functionality is fully compatible. However, due to some of the App Engine limitations, a number of the additional functions may not work correctly.
Logging
Google uses java.util.logging, also referred to as the JDK 1.4 logging. Apache Wink uses slf4j. In order to enable Wink's logging function, replace the slf4j-simple-<version>.jar with the slf4j-jdk14-<version>.jar.
In order to view all of Wink's messages place the following property in the logging.properties file:
| No Format |
|---|
org.apache.wink.level=ALL |
Everything that the servlet writes to the standard output stream (System.out) and standard error stream (System.err) is captured by the App Engine and then recorded in the application logs.
| Info | ||
|---|---|---|
| ||
In order to gain an in depth understanding refer to Logging. |
| Tip |
|---|
When running with Spring, make sure that you have |
Additional Issues
The following section contains "additional Issues" that maybe experience while trying to run custom developer code in the Google App Engine. It is advantageous to read the relevant documentation as it provides important information, that will save valuable developer time that is required to ascertain why the application behaves differently in comparison to a regular servlet container.
Context Path
Usually the URI in a servlet container looks like this:
| No Format |
|---|
requestURI = contextPath + servletPath + pathInfo |
while in most servlet containers context path is a war name (or it can be configured), in App Engine it's just empty.
So if your servlet is mapped to "rest", access
| No Format |
|---|
http://host:port/rest |
.