GWT 编译

GWT project 编译不同的模块时，花费的时间比较长。在iis 上还要自己去发布。每次都是重复动作。

eclipse 调试访问数据库的代码的时候需要去掉appengine. 这样就不会报 data deny 的错误。如果想通过tomcat 来调试需要设置为tomcat 工程。并将tomcat 下面的server.xml

添加  <Context path="/Demo" docBase="C:\Demo\war" crossContext="true" debug="0" />

这样使用gwt 编译后的文件不用再进行调整就是个完整的工程可以部署在tomcat 上,gwt-usr.jar 需要删除javax.servlet 文件。如果有其他问题，就需要检查catalina 的策略。放开权限。

tomcat 插件com.sysdeo.eclipse.tomcat_3.3.0 可以下载。

Combining TestCase classes into a TestSuite

The GWTTestSuite mechanism has the overhead of having to start a development mode shell and servlet or compile your code. There is also overhead for each test module within a suite.

Ideally you should group your tests into as few modules as is practical, and should avoid having tests in a particular module run by more than one suite. (Tests are in the same module if they return return the same value from getModuleName().)

GWTTestSuite class re-orders the test cases so that all cases that share a module are run back to back.

Creating a suite is simple if you have already defined individual JUnit TestCases or GWTTestCases. Here is an example:

public class MapsTestSuite extends GWTTestSuite {  public static Test suite() {    TestSuite suite = new TestSuite("Test for a Maps Application");    suite.addTestSuite(MapTest.class);     suite.addTestSuite(EventTest.class);    suite.addTestSuite(CopyTest.class);    return suite;  }}