Simplified and fast Java quick development framework lml overall architecture Preview

First of all, this is only the overall architecture preview, not unchangeable. I just strive to be simple, not to adapt to various project environments, so you can modify and expand as needed. However, my theme has always been simple and fast, so we should try to avoid unnecessary complexity and seize the lead quickly.

I am using the English version of myeclipse8.5 for development. The upgrade is time-consuming and has never been upgraded (my living environment is poor and I cannot access the Internet ). Good development tools can multiply the development efficiency, which may be why C # development efficiency is so high. VS is always a super development tool in my mind. Various plug-ins provided by myeclipse are also quite handy, which is much easier to install than eclipse. Using myeclipse, you can easily import the packages required by SSH. If some shoes use eclipse or other tools, you may need to configure them on your own.

1. the SSH import package is as follows:

 

2. In addition to the SSH package, you also need to import the MySQL driver package, c3p0 connection pool package, and velocity packages. Of course, there are also constantly improved lml packages. For example:

 

3. The following section describes the SRC section. SRC mainly includes HBM: used to store hibernate database ing files. The ing files in this package can be usedCodeGenerate tools, and myeclipse provides corresponding plug-ins. Action: The action package mainly stores the action class of the project. The action package needs to be divided into sub-packages. The sub-packages correspond to the concept of "area, the first article mentioned it in simple search. If you do not know it, you can take a rough look. Model: an object class package that stores Java Beans that correspond to database tables in a one-to-one manner. You can use the corresponding plug-ins provided by myeclipse to quickly generate a model. Others: You can expand it as needed.

 

 

4. Each Action Sub-package contains several actions, and each action contains several methods. In the lml framework, we enter a link address in the address bar of the browser to access the corresponding method in the corresponding action.

 

5. View and method. Unless otherwise specified, each method must correspond to a view with the same name. This same name is necessary. In lml, we think that conventions are better than configurations. Similar to the correspondence between methods and views, it is really unnecessary to use a large number of configurations or many annotations to specify them. A simple convention solves all these complicated problems!

 

6. Others. CSS, JS, and other resource files that need to be used in the project can be freely organized without any conventions or restrictions.

I am not good at describing a framework. I just open the project, cut a few pictures from top to bottom, and then draw a little bit. In general, this framework looks like this, which is very simple. It is simple to use only a jar package I wrote myself. I will introduce this package in detail later with the source code. Because it is simple, so fast.

Fish and bear's paw cannot have both sides. If we have been pursuing rapid development, we should not use a heavy framework. The complexity of the framework will certainly increase the development time, and will certainly bring a considerable workload to the maintenance. As users, we should know how to choose and how to choose.

Next set preview: Framework Configuration