Quick Development Framework for enterprises-Based on configuration files

Today, I saw two articles on enterprise development in javaeye. Article . ( A. Forget about Puyuan EOS and build your own enterprise-level Rapid Application Development Platform B. Splash of cold water on people who make quick development frameworks)

My company also has its own quick development framework. In a brief introduction, if you have any questions, please submit them.

The basic component is a basic framework, a workflow engine, a process management engine, and an integrated skeleton similar to ESB.

1. Basic Framework functions:

Integrated permission management. Is the portal of the entire system. Its core function is to generate an application Page Based on the configuration file. (Permission configuration, addition, deletion, modification, multi-Table operations, data verification, multiple controls dropdownlist, checkbox, Treeview ..).

2. workflow engine, business flow, and forms. The process description language is xpdl. Use open-source tools to draw Processes

3. The implementation of the process management engine is the same as that of the workflow engine (with the same kernel and slightly changed interfaces). The user of the engine is a system or software. Call different services through a set process to implement complex business logic

4. Integrated SKELETON: equivalent to a portal inside the system. internal services of the enterprise are registered on the skeleton. It also acts as an adapter. The basic framework has extended interfaces. Services integrated on the skeleton can implement interfaces of the basic framework.

The solutions mainly include:

I. Centralized permission management. If every time a system is developed and has a permission module, no matter whether it is development or maintenance, it is very troublesome. Even if you use DLL encapsulation, however, you still need to create a table. If a person leaves the company, you may have to delete users from multiple systems. Now the system entry is like this, and the permission is still the ad authentication integrated with IIS.

2. Eliminate most duplicatesCode. Enterprise-level development, a large part of which is for database or system development that maintains data. There are inevitably many addition, deletion, and modification operations. Code Generator is a "good" idea. Why do I add quotation marks? I think code generation has a dual nature: A. It is really simple. B is actually complicated. In simple terms, a lot of interfaces and layer-3 architecture are generated at the time of "break. The complexity is that during maintenance, the code looks like nothing to do. Without comments or tests, you do not dare or know where to modify it. Currently, basic data maintenance is a configuration file and pages are dynamically generated. Fewer errors.

3. Create a workflow. Large enterprises cannot run the signing program without a framework. A process can keep you busy for several months. Permission allocation, process direction, flow chart, and process management are not the best examples. There are many good open-source frameworks, but most of them are Java. If you want to share a. Net Development Team, hope the tools will sigh. If you have the money, you can always buy it, but the data that the process runs is often needed in the business. As a result, it is not easy to develop a process.

At the same time, the computer can also run the process, which is defined like the process, but the resource is a service rather than a person, and the computing is done rather than a signature.

4. Function reuse. We often do a lot of repetitive work when developing different systems. In addition to the previous permissions, add, delete, modify, and so on, sometimes large modules will also copy, for example, querying the production order information from SAP. Raw material management system. Production management systems and quality management systems are required. The common method is to separate the three systems. Now, the basic framework web extension can be used as an enemy.

As mentioned above, it is the benefit of developers and the benefit of users. It is better to get familiar with a single interface than to get familiar with a lot of interfaces. I open a browser to handle most transactions.

Specific configuration attributes. Originally, XML was used to write down the architecture at home,

Basic Framework

Page title // basic page information

Roles name, type // role name, permission type

Tables name, alias, PK // data table name, alias, primary key

Fields name, table, type, alias // field configuration (optional), table, alias, Data Type

Controls widthunit (the width is calculated proportionally. If the value of widthunit is 5, and the total number of controls is 1, the width of the control is 20%)

+ Dropdownlist name, field, wideunit, valuesourse/values // control configuration, field, width, data source,

+ Extendbutton name, field, servicename, parmsfield

Others include the upload control, Date input control, Treeview, and various selection controls.

Grid width, widthunit, fields, type, // list area, field, permission category

+ Parents field, table, childrens, // key fields containing the word table, Word Table name, and sub-table fields ..

+ Link field, formatstring, valuefields // link field, link Format String, used for formatting Value Field

+ Extend field, servicename, parmsfield // Extended Function Field, service name, parameter field

Childgrid // The Sub-table and List areas are basically the same.

 

The basic framework configuration is basically here. Configure the process and try again later.