Java Development in Linux Environment (vii): The Open source framework of "The flower is becoming attractive"

Jiangnan white dress in September 2005, on his blog put forward: Each team should have a appfuse-style project to demonstrate the team's current system framework and design patterns. There are a dozen benefits to this project: providing common library Stack for all projects, providing the most reliable code blueprint, ensuring consistent patterns and code style, speeding up the spread of knowledge across the team, facilitating the integration of new people, and providing a stable and concise environment for test code. Moreover, the construction or use of such a project to adhere to a few iron discipline: one is to force the update, all team approval of the latest models are to refactor to Myappfuse; second, the standard update, each update must be strictly tested and write update records, transplant documents; three is mandatory copy Start, all code must be copy from the Myappfuse instead of the code that you like to find any item. Please visit the South-white blog.

2005 years later, a variety of full-stack framework is springing up, Jiangnan white dress their own frame, it evolved into a springside. This frame, is also my most favorite.

I'm sure it's impossible to understand every framework, so I'm only going to get my attention in the last few days, and let me be a little bit of a heartbeat.

The first one, of course, is Springside 2.0, the current version is still RC1, but does not affect our use, and from the RC version to the official version will not add new features, just modify the bug, so we can safely apply it to our project, do not need to worry about the impact of the version update. The advantages of Springside 2.0 are as follows:

1, automatic management of various components, we only need to download Springside All-in-one on the line, do not need us to go everywhere to find a variety of open source components. When used, Springside provides a very useful IDE plug-in that will automatically help us build the directory structure of the project, copy the components we specify, and integrate them when building the project. We do not need to modify a single line of configuration files, these springside all help us to do. We can put all our energies into the business logic.

2, clear code structure, Springside for multi-layer architecture of the hierarchy is very clear, all levels of MVC provides a very good base class, we only need to expand on these classes. Springside has a very consistent code specification and is comfortable to write code. There is very good guidance in the springside where the code should be placed in the project, and there will be no structural confusion about the north. Springside Specifies the customary usage of the configuration file for each component in its writing and placement.

3, the test provides a sound support, for the DAO layer provides a very good test base class, for the control layer and the view layer, we can use the integrated test method, and Springside also for us to integrate a very good integrated test framework selenium. All in all, in the process of using Springside, I did not have the effort to find another component, nor did I use any complex mock techniques, and simply use the functions provided by Springside to complete a variety of automated tests conveniently.

4, comprehensive and detailed development of documents, but also the whole Chinese Oh.

The second one is Grails, the current version of 0.6, although it's not yet 1.0, but it's already hot, the magic of the component rails framework. Mountain Boy's evaluation of it is "at first sight, Farewell to Love", for me, of course, is also a little heartbeat. The advantages of grails, I think also have the following points:

1, the use of dynamic scripting language groovy, the language received in the form of C, Java, C #, JavaScript, and so on, the most obvious feature is the use of {}, semicolon, etc. as a separator for program code. This language is very poetic, I like it. And groovy is a dynamic language, the advantage of dynamic language is that the brain how to write the program, no longer restricted to the static language of the program structure and data types.

2. Grails uses Ruby on Rails's "Protocol Programming" (Coding by convention) Paradigm to reduce the need for configuration files and other boilerplate code. With protocol programming, if the name of the file itself describes the purpose of the file, you do not need to declare the content again in the configuration file. This frame looks at the file name and makes clear the purpose of the file. Do not configure the file, write the program to be more comfortable.

3. Grails uses the open source framework of spring and hibernate, which means that what we have learned in the past will not be in vain.

Grails is not launched two days a day, it is mentioned here, mainly because the Grails Authority Guide is coming out. Eager to.

The third thing to introduce is our own development of a JSF based on the code of the Open source framework: Operamasks, its backstage is Kingdee. Jiangnan White is a cow, Kingdee is a cattle company. As we all know, he is a relatively small number of continued in the Java Middleware Field research and development and achieved a certain degree of manufacturers. His application server was the first to be certified through Java EE5, and he now joins the JCP Committee of Java EE.