development details

1: The code submitted to SVN must have a submission note for easy viewing later.

2: If you consider page caching, you can add a random number after the path: url + "&TimeS=" + Math.random();.

3: Class header comments: class description, author, version, special description.

4: The method must have comments: method description, parameter list meaning.

5: There are no special requirements, the list page will display 10 pieces of data, and 15 pieces of data need to be displayed in the pop-up box.

6: The list page must have four buttons: add, delete, modify, and detail. The name sequence function cannot be modified. If special functions are required, add a special function button behind the four buttons.

7: The log page of the sub-tables will always display the data of this week or this month, but not all data of all tables.

8: The detailed page should be implemented with a pop-up box as much as possible.

9: The service interface provided externally must be under the service package.

10: Whether it is Java code or Js function, it is not allowed to use the original name directly after copying other people's code. It must be named after its own module and business. For example, platform users add commUserAdd().

11: All paths in the system, except in special cases, must use absolute paths.

12: For printing in the system, even for debugging, you must use Log to print, and the words System.out.println() are not allowed to appear in the system.

13: There are no special requirements. It is not allowed to use the asynchronous loading method for cascading operations or to obtain relevant information. The method of pop-up box must be used. The specific pop-up box background code and the path of the front page must be specified by the team leader.

14: The name of the database table must not be inconsistent with the name of the table, the name in the configuration file, and the name in JDBC. This system recommends: system-module-business entity class name.

15: Without special cases, character fields must not use null characters or/and other default values, and should default to Null.

16: For an object with many fields and the same way of setting the field attributes when creating, it is recommended to use the constructor of the entity class to implement it. It is not allowed to have repeated and cumbersome functions in the system. Set the same after creating the object. The code for the attribute value.

17: For the creation of DWR objects, always use New instead of the Spring container.

18: For integer fields stored in the database that do not need to perform related calculations, statistics, etc., Int is not allowed, and char(1) must be used.

19: The field name in the database must be consistent with the field name of the entity class, so as to facilitate the platform to provide public methods and the convenience of later maintenance.

20: Do not modify the system style, modify the public implementation, store files at will, and must keep the overall style consistent with the system.



Please go to the ITEYE website to see the original, thank you!

http://cuisuqiang.iteye.com/ !