Shulou(Shulou.com)06/02 Report--

Where is the J-Hi rapid development platform? I believe many inexperienced people are at a loss about it. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

1. Get started quickly and reduce the learning curve

For those who are new to J-Hi, it is easy to get started, we provide floating help for every function point, and even without any information (of course, we have provided video and development documentation), you can create your own project prototype in ten minutes with guide and help.

Secondly, the J-Hi platform mostly uses the familiar mainstream framework and technology, if you know something about the mainstream framework, then there is no resistance to the learning of J-Hi.

2. Quickly build the development environment

Maybe you will adopt different framework technologies because of your project or your own development team, for example, there are far more people on your team who are familiar with struts2 than engineers who master webwork, or there are many statistical analysis functions in your project, you have to consider the efficiency of ORM, and you have to give up hibernate to adopt ibatis or springJDBC, maybe you also have to consider database issues, and so on. You must consider many factors in building a development environment. Although building a development environment is not complex, it is not automated enough, and manual configuration is time-consuming and laborious. J-Hi provides a reasonable solution for quickly building a development environment, and you can build a dynamic development environment according to your needs.

Here you can choose different ORM frameworks

Here you can choose different presentation layer frameworks

Here you can choose different page frames, and we provide a "preview" so that you can see the display of the built page before you build the development environment.

Here you can select different databases.

3. Generate all the code quickly

By creating or importing schemas, you can quickly generate all code and files, and automatically adapt to the framework technology you choose and the database.

Of course, you can also choose to generate part of the code file, such as only JSP pages or only java code. The structure of the generated java code is as follows (because the framework I chose is ibatis3+struts2, the platform automatically matches things that only generate class files related to these two frameworks, but not useless other frameworks):

4. Quickly solve the technical difficulties in the business requirements

Generally speaking, when we do project development, we always have to wait until the middle and later stage of project development to solve the core business problems, so it is impossible to reasonably estimate the technical risk of the project. The reason is that complex business always has to wait until the basic module is built before entering the development stage, so as to solve the core technical problems behind. Let's take an expense claim as an example to make a simple explanation, such as the business logic of reimbursement after audit is very complex and may also involve docking with other systems. Generally speaking, we always have to wait until this reimbursement form is built, and at least have the most basic add, delete, query and change function (even if there is no page, there must be background code) before we can enter the development of the core business, which increases the technical risk. because we will find the problem early, but solving these problems lags far behind finding this problem. Even in the middle and later stages of development, they have to change again and again at the bottom because of technical problems. Using J-Hi can quickly get into the technology of the business core, because as long as it is generated, the basic functions are already provided, and even the platform provides you with unit test case classes, so that you can point directly to the business core and control the project risk in *.

5. By providing common components

The platform provides many common business components, such as organization, role permissions, reports, timing tasks, menu management, log management, system configuration, attachment upload and so on. In addition, the platform also provides some pure technical components, such as tree structure, java script tools, code generator, optional return JSON objects and so on. These common business and technical components can save you a lot of time in the development process and can be used on demand, thus greatly reducing the speed of development.

6. Improve the development speed through the reusability of services

Before we introduce the service reusability of the platform, let's give an example. For example, you have done an OA project in which there is a module of reimbursement management. This module is very mature, and you have been using it in the OA system for a long time. Now there is another ERP system, and you want to copy this mature claims management to the ERP system, so that this feature does not have to be developed in the ERP system. For the platform, this is the reuse of services, we provide a complete set of solutions for service reusability, and have their own visualization tools.

We call it the J-Hi Integration tool, which is made in C #. What it does:

1) visually import / export databases, and implement cross-database at the same time. For example, you can develop (export) on mysql and migrate all data to oracle (import).

2) publisher, which visually publishes the module or system you develop into a distribution package (including database, jar, file [jsp, js, picture, configuration file, etc.] and fragments of the file [such as modifying part of the web.xml file])

3) deployer, deploy the release package to the development project. The deployed content is described in the publisher.

4) the implementer, the corresponding production system, we automatically deploy the corresponding files and databases to the production system through FTP.

7. Rapid deployment and migration

Maybe you are upset by the customer's request to change the SQLServer database to Oracle, because it requires a lot of data migration, or you are frustrated by repeatedly deploying the modified bug to the production environment. I think J-Hi provides you with a convenient way through its integration tools. For specific implementation, please see the introduction in the previous section.

8. Developers can take over other people's jobs quickly

Because using J-Hi development, the generated code and file style are the same, where to write business logic how to write? Where should I change the page? what should I do? Which database table or table correspondence to the class do you want to go to? The naming rules for generated classes, JSP files, and configuration files are all unified. So a newcomer to join the team will be easy to get started and get into the working state, even if it is to modify the code written by others, it will quickly locate the corresponding location to be modified.

9. Quickly resolve requirements changes

For project development, it is normal for project requirements to change, and for experienced project managers, it is abnormal if a project has never changed requirements:) but most of the requirements changes have to change the database table. if it is a stable system, this kind of change is really fatal. J-Hi also provides its own solution for this, and for simple table changes, the platform only needs to generate a single entity. If it is a complex change, we also provide a solution for inheriting entities, that is, all the original code and table structure remain unchanged. J-Hi will form a set of inheritance relationships from database tables to java classes and then to JSP pages through entity inheritance, thus ensuring the stability of previous functions. This seems mysterious. Let's give an example. For example, you have a department table, N multi-information is related to it, and do a lot of business processing, and now customers ask to add some other information to the department table. For you, you may add fields to the department table, resulting in changes in all classes and pages, and the system has been stable for a year or two, and the developers have left the company. in this way, the person who takes over has to understand all the code before it is possible to change, resulting in a great reduction in the speed of development. The platform provides another solution: don't touch anything before, and it's about putting a patch on the original basis. Make another table to form an one to one relationship between this table and the department table, and the classes, whether POJO, DAO, Service, all inherit from the corresponding department class as the parent class, and all the elements of all departments are inherited on the JSP page, thus forming an entity inheritance relationship, which is like the most basic "opening and closing principle" in the design pattern, which is open to all new functions and closed to existing old functions. You can completely regard the old function as a black box. This can not only ensure the stability of the existing functions, but also add new functions as a supplement.

After reading the above, have you mastered the method of how fast the J-Hi rapid development platform is? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.