Google Engine: Error: NOT_FOUND
The app works well. But after we deployed version 4, it showed this error:
Error: NOT_FOUND
There is no other message.
You can see it here . When deploying eclipse, success message appears: Task7 deployed successfully to Google App Engine
All previous versions still work well. The local version also works fine. Tried looking for similar problems and found a few ( 1 , 2 , 3 ) but none of them have any useful solutions.
I don't know if web.xml will help figure out the solution, but I am giving it here. Although I checked and found the web.xml in the previous version (it works well) and it looks like it.
<?xml version="1.0" encoding="utf-8" standalone="no"?><web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
<servlet>
<servlet-name>controller</servlet-name>
<servlet-class>ebiz.pbj.task7.controller.Controller</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>controller</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>controller</servlet-name>
<url-pattern> /start </url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file> start </welcome-file>
</welcome-file-list>
<servlet>
<servlet-name>SystemServiceServlet</servlet-name>
<servlet-class>com.google.api.server.spi.SystemServiceServlet</servlet-class>
<init-param>
<param-name>services</param-name>
<param-value/>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>SystemServiceServlet</servlet-name>
<url-pattern>/_ah/spi/*</url-pattern>
</servlet-mapping>
<filter>
<filter-name>ObjectifyFilter</filter-name>
<filter-class>com.googlecode.objectify.ObjectifyFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>ObjectifyFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
</web-app>
If you need any other code snippets please let me know and I will edit my question.
In fact, he was embarrassed about what went wrong. Any help would be greatly appreciated. Thank.
source to share
I think I should share my findings in case anyone else falls into the same problem.
This might not be the only reason for the problem, because 404: NOT_FOUND can happen for a variety of reasons, but this is one reason and people should be aware of it.
Jsp file naming is case sensitive . In the controller, we have codes like this:
if (errors.size() != 0)
{ return "login.jsp"; }
but ours login.jsp
was wrongly named login.jsp
- so he couldn't find it.
source to share