Is the war directory used by the GWT compiler as both an input and output directory to the compiler process?
In GWT 1.6, the compiler generates output in a directory structure following the Web Application Archive (WAR) standard layout. This is a newly introduced feature that makes it easier to deploy your application on any servlet container, like Jetty, Tomcat, or the Google App Engine Java runtime. See Chapter 9 of the Servlet 2.5 API specification for more details on the WAR standard layout. Following the convention, developers may place their static resources, including their host HTML page, in the war/
Starting with GWT 1.6, the compiler generates output in a directory structure following the Web Application Archive (WAR) standard layout. This feature makes it easier to deploy your application on any servlet container, like Jetty, Tomcat, or the Google App Engine Java runtime. See Chapter 9 of the Servlet 2.5 API specification for more details on the WAR standard layout. Following the convention, developers may place their static resources, including their host HTML page, in the war/
Related Questions
- When compiling I get "Could not copy temporary files to the output directory" or "The process cannot access the file because it is being used by another process" error messages. Why?
- Is the war directory used by the GWT compiler as both an input and output directory to the compiler process?
- what are the channels used for input & output operations?, what is the sender veto for that connection only?
