CN108572823B - Front-end and back-end development management method and system based on interface engine - Google Patents
Front-end and back-end development management method and system based on interface engine Download PDFInfo
- Publication number
- CN108572823B CN108572823B CN201810368902.9A CN201810368902A CN108572823B CN 108572823 B CN108572823 B CN 108572823B CN 201810368902 A CN201810368902 A CN 201810368902A CN 108572823 B CN108572823 B CN 108572823B
- Authority
- CN
- China
- Prior art keywords
- configuration
- interface
- end equipment
- interface engine
- configuration file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/315—Object-oriented languages
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Computing Systems (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides a front-end and back-end development management method and a system based on an interface engine, wherein the method comprises the following steps: the back-end equipment develops to obtain an interface template, and the interface template can provide a configuration file format for the front-end equipment; the front-end equipment configures the configuration items according to the configuration file format and stores configuration information of each configuration item to generate a configuration file; the back-end equipment develops an interface engine, reads the configuration information of each configuration item in the configuration file through the interface engine, and dynamically generates an interface access address according to the configuration information; and the front-end equipment accesses data according to the interface access address. According to the front-end and back-end development management scheme, the interface engine is obtained through development, the interface engine is utilized to read the configuration information of each configuration item in the configuration file, and a data access interface is provided for the front-end equipment, so that the defect of a large amount of modification work during subsequent docking caused by simulated false data in the prior art is overcome, data modification during subsequent docking is reduced, and development efficiency is improved.
Description
Technical Field
The application relates to the technical field of software development, in particular to a front-end and back-end development management method and system based on an interface engine.
Background
With the development of internet technology, various websites gradually enter the lives of people, the front end of a webpage is an important branch of the internet technology and occupies an extremely important position in the aspects of interface display and user interaction, and meanwhile, more and more back-end business logics are gradually frontized, so that the front-end business logics become increasingly complex. In a traditional development mode, a front end is generally responsible for developing static pages, virtual fake data, preprocessing business logic and the like, and after a rear-end interface is developed, corresponding fields are modified for butt joint. After the front end and the back end are respectively and correspondingly developed, when the front end and the back end are butted, if the fields fed back by the back end do not correspond to each other and the data structure does not correspond to each other, a large amount of modification is carried out on the front end, and the development burden is increased.
Disclosure of Invention
In view of the above, the present application provides a front-end development management method and system based on an interface engine to improve the above problem.
The embodiment of the application provides a front-end and back-end development management method based on an interface engine, which comprises the following steps:
the back-end equipment develops to obtain an interface template, and the interface template can provide a configuration file format for the front-end equipment;
the front-end equipment configures configuration items according to the configuration file format and stores configuration information of each configuration item to generate a configuration file;
the back-end equipment develops an interface engine, reads the configuration information of each configuration item in the configuration file through the interface engine, and dynamically generates an interface access address according to the configuration information;
and the front-end equipment performs data access according to the interface access address.
Optionally, the method further comprises:
the back-end equipment is designed to obtain a data structure simulated in a key value pair mode;
and reading the data structure by using the interface engine according to the configuration information of each configuration item in the configuration file, and generating a corresponding field mapping for the front-end equipment to use according to the data structure, wherein the field mapping comprises a mapping relation between an interface field of the front-end equipment and an interface field of the back-end equipment.
Optionally, the interface engine includes a front-end configuration page, and the method further includes:
when the front-end equipment is in butt joint with the back-end equipment, whether the interface fields of the front-end equipment and the back-end equipment are matched or not is detected according to the field mapping;
and if not, the front-end equipment modifies the data structure on the front-end configuration page.
Optionally, the step of reading, by the interface engine, configuration information of each configuration item in the configuration file, and dynamically generating an interface access address according to the configuration information includes:
reading the configuration information of each configuration item in the configuration file by using a java reflection mechanism through the interface engine;
initializing a database, inserting the configuration information of each configuration item into the database, and dynamically generating an interface access address according to the configuration information of each configuration item.
Optionally, the step of configuring, by the front-end device, configuration items according to the configuration file format, and storing configuration information of each configuration item to generate a configuration file includes:
the front-end equipment sends the request information of the configuration items to the back-end equipment through a request address according to the configuration file format;
after the request is successful, the back-end equipment feeds back response information corresponding to the request information to the front-end equipment;
and the front-end equipment completes the configuration of the configuration item according to the response information and stores the configuration information of the configuration item to generate a configuration file.
Optionally, the request information includes a request parameter, request header information, and a request type, and the response information includes response data, response header information, and a response type.
The embodiment of the application also provides a front-end equipment development management system based on the interface engine, the system comprises front-end equipment and back-end equipment which can establish communication connection, the front-end equipment comprises a configuration module and an access module, and the back-end equipment comprises an interface template development module and an interface access address generation module;
the interface template development module is used for developing the back-end equipment to obtain an interface template, and the interface template can provide a configuration file format for the front-end equipment;
the configuration module is used for configuring configuration items according to the configuration file format and storing configuration information of each configuration item to generate a configuration file;
the interface access address generation module is used for developing an interface engine, reading the configuration information of each configuration item in the configuration file through the interface engine, and dynamically generating an interface access address according to the configuration information;
and the access module is used for accessing data according to the interface access address.
Optionally, the backend device further includes a data structure obtaining module and a field mapping generating module;
the data structure acquisition module is used for designing and obtaining a data structure simulated in a key-value pair mode;
the field mapping generation module is configured to read the data structure by using the interface engine according to the configuration information of each configuration item in the configuration file, and generate a corresponding field mapping for the front-end device to use according to the data structure, where the field mapping includes a mapping relationship between an interface field of the front-end device and an interface field of the back-end device.
Optionally, the interface engine includes a front-end configuration page, and the front-end device further includes a detection module and a modification module;
the detection module is used for detecting whether the interface fields of the front-end equipment and the back-end equipment are matched according to the field mapping when the front-end equipment and the back-end equipment are in butt joint;
the modification module is used for modifying the data structure on the front-end configuration page when the interface fields of the front-end equipment and the back-end equipment are not matched.
Optionally, the interface access address generating module includes a reading unit and a generating unit;
the reading unit is used for reading the configuration information of each configuration item in the configuration file by using a java reflection mechanism through the interface engine;
the generating unit is used for initializing a database, inserting the configuration information of each configuration item into the database, and dynamically generating an interface access address according to the configuration information of each configuration item.
According to the front-end and back-end development management method and system based on the interface engine, the back-end equipment develops to obtain the interface template, the front-end equipment configures the configuration items according to the configuration file format included in the interface template, and stores and generates the configuration file. And the back-end equipment develops to obtain an interface engine, and reads the configuration information of each configuration item in the configuration file through the interface engine to obtain an interface access address. And the front-end equipment accesses data according to the interface access address. According to the front-end and back-end development management scheme, the interface engine is obtained through development, the interface engine is utilized to read the configuration information of each configuration item in the configuration file, a data access interface is provided for the front-end equipment, the defect of a large amount of modification work during subsequent butt joint caused by simulated false data in the prior art is overcome, the development is enabled to be more in line with the requirement, data modification during subsequent butt joint can be reduced, and the development efficiency is improved.
In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
Fig. 1 is a schematic view of an application scenario of a front-end and back-end development management method based on an interface engine according to an embodiment of the present application.
Fig. 2 is a schematic structural block diagram of a front-end device according to an embodiment of the present application.
Fig. 3 is a schematic structural block diagram of a backend device provided in an embodiment of the present application.
Fig. 4 is a flowchart of a front-end development management method based on an interface engine according to an embodiment of the present application.
Fig. 5 is a flowchart of the substeps of step S120 in fig. 4.
Fig. 6 is another flowchart of a front-end development management method based on an interface engine according to an embodiment of the present application.
Fig. 7 is another flowchart of a front-end development management method based on an interface engine according to an embodiment of the present application.
Fig. 8 is a functional module block diagram of a front-end and back-end development management system based on an interface engine according to an embodiment of the present application.
Fig. 9 is a functional block diagram of an interface access address generation module according to an embodiment of the present application.
Fig. 10 is another functional block diagram of a front-end and back-end development management system based on an interface engine according to an embodiment of the present application.
Fig. 11 is another functional block diagram of a front-end and back-end development management system based on an interface engine according to an embodiment of the present application.
Icon: 10-front-end development management system based on interface engine; 100-front-end equipment; 110 — a first development management device; 111-configuration module; 112-an access module; 113-a detection module; 114-a modification module; 120-a first processor; 130-a first memory; 200-back end equipment; 210-a second development management device; 211-interface template development module; 212-interface access address generation module; 2121-a reading unit; 2122-a generating unit; 213-data structure acquisition module; 214-field mapping generation module; 220-a second processor; 230-second memory.
Detailed Description
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
Please refer to fig. 1, which is a schematic view of an application scenario of a front-end and back-end development management method based on an interface engine according to an embodiment of the present application. The scene includes a front-end device 100 and a back-end device 200, where the front-end device 100 and the back-end device 200 can establish a communication connection to perform data communication or interaction. In this embodiment, the front-end device 100 may be a terminal device held by a front-end developer, the back-end device 200 may be a terminal device held by a back-end developer, and the front-end device 100 and the back-end device 200 may be, but are not limited to, a computer, a server, and other terminal devices having a data processing function.
Referring to fig. 2, a schematic structural block diagram of a front-end device 100 according to an embodiment of the present disclosure is provided, in the embodiment, the front-end device 100 includes a first development management apparatus 110, a first processor 120, and a first memory 130, where the first memory 130 is directly or indirectly electrically connected to the first processor 120 to implement data transmission or interaction. The first development management apparatus 110 includes at least one software function module which may be stored in the first memory 130 in the form of software or firmware or solidified in the operating system of the front-end device 100. The first processor 120 is configured to execute an executable module stored in the first memory 130, such as a software functional module or a computer program included in the first development management apparatus 110.
Referring to fig. 3, a schematic structural block diagram of a backend apparatus 200 according to an embodiment of the present disclosure is provided, in the embodiment, the backend apparatus 200 includes a second development management device 210, a second processor 220, and a second memory 230, where the second memory 230 is directly or indirectly electrically connected to the second processor 220 to implement data transmission or interaction. The second development management device 210 includes at least one software function module that can be stored in the second memory 230 in the form of software or firmware or solidified in the operating system of the backend apparatus 200. The second processor 220 is configured to execute an executable module stored in the second memory 230, such as a software functional module or a computer program included in the second development management device 210.
Please refer to fig. 4, which is a flowchart illustrating a front-end and back-end development management method based on an interface engine according to an embodiment of the present application. It should be noted that the methods provided herein are not limited by the specific order depicted in fig. 4 and described below. The respective steps shown in fig. 4 will be described in detail below.
In step S110, the back-end device 200 develops an interface template, which can provide a configuration file format for the front-end device 100.
Step S120, the front-end device 100 configures configuration items according to the configuration file format, and stores configuration information of each configuration item to generate a configuration file.
In the process of project development, page development of a front end, application development of a back end and the like are often involved, and when the front end does not receive required data returned by the back end and the back end does not provide implementation logic, writing some dummy data is often adopted to perform subsequent business development. However, when the front end and the back end are subsequently connected, if the field and the data structure actually fed back by the back end do not correspond to the data simulated by the front end, a large amount of data modification is required, and the development burden is increased. In this embodiment, an interface engine is developed, and the interface engine is used to provide an interface access address based on the requirement of the front-end device 100, so as to provide data access for the front-end device 100. The defect of frequent subsequent changes caused by the need of simulating false data by the front-end equipment 100 is avoided.
In this embodiment, the back-end device 200 develops an interface template, which can provide a configuration file format for the front-end device 100. The interface template can provide functions of data addition, deletion, modification, query, paging and the like, and can be used for expanding other common functions subsequently according to requirements.
The front-end device 100 configures the configuration items according to the configuration file format, optionally, the configuration items are displayed on a configuration page of the front-end device 100, and a front-end developer fills configuration information on the configuration page according to a requirement to complete configuration. Optionally, referring to fig. 5, in the present embodiment, the step S120 may include three substeps, namely step S121, step S122 and step S123.
In step S121, the front-end device 100 sends the request information of the configuration item to the back-end device 200 through a request address according to the configuration file format.
In step S122, after the request is successful, the back-end device 200 feeds back response information corresponding to the request information to the front-end device 100.
Step S123, the front-end device 100 completes configuration of the configuration item according to the response information, and saves the configuration information of the configuration item to generate a configuration file.
When the front-end device 100 performs configuration, after the front-end developer completes filling the corresponding configuration information, the request information of the configuration item is sent to the back-end device 200 through the request address. The request information includes request parameters, request header information, request type, and the like. After the request is successful, the back-end device 200 feeds back response information corresponding to the request information to the front-end device 100. Wherein the response information includes response data, response header information, and a response type. The front-end device 100 completes configuration of each configuration item according to the received response information, and saves the configuration information of the configuration item to generate a configuration file.
Step S130, the backend device 200 develops an interface engine, reads the configuration information of each configuration item in the configuration file through the interface engine, and dynamically generates an interface access address according to the configuration information.
Step S140, the front-end device 100 accesses data according to the interface access address.
In this embodiment, an interface engine is developed by the backend device 200, and the interface engine is a system that dynamically generates an interface address accessible by the front end by using a specific server program (such as a program made by Java Web) according to the configuration information. The interface engine may include an interface configuration reader, an interface generator, a database operator, an exception generator, and a front-end configuration page. The interface engine mainly dynamically generates an interface address through configuration information, wherein the interface address can be an address for acquiring data such as music comments or a webpage address.
Specifically, the backend device 200 may read the configuration information of each configuration item in the configuration file through the interface engine by using a java reflection mechanism. And initializing a database, inserting the configuration information of each configuration item into the database, and dynamically generating an interface access address according to the configuration information of each configuration item.
With the above arrangement, the front-end developer can obtain the back-end interface address generated by the interface engine, rather than the address simulated by the front-end device 100, by only filling the interface configuration item without writing the back-end code. Therefore, the purpose of simulating development in a real server environment under the condition that the back end does not return data required by the front end can be achieved.
Optionally, referring to fig. 6, in this embodiment, the method may further include the following steps:
in step S210, the backend device 200 designs a data structure simulated in a key-value pair form.
Step S220, reading the data structure by using the interface engine according to the configuration information of each configuration item in the configuration file, and generating a corresponding field mapping according to the data structure for the front-end device 100 to use, where the field mapping includes a mapping relationship between an interface field of the front-end device 100 and an interface field of the back-end device 200.
In this embodiment, a set of data structures simulated by a key-value pair format is designed, and the data structures refer to data corresponding to a front-end interface. The interface engine may be utilized to read the data structure and generate a corresponding field map for providing to the front-end device 100, where the field map includes a mapping relationship between the interface fields of the front-end device 100 and the interface fields of the back-end device 200, such as { key (representing the field name used by the front-end device 100): value (field name representing the backend apparatus 200 needs to use) }. For example, the front-end device 100 uses "name" for the reference to the name, the backend device 200 uses "name" for the reference to the name, and the mapping relationship between the two is name: and (7) nam. Therefore, when the subsequent docking is carried out, whether the interface fields of the two meet the pre-established relationship or not can be detected according to the mapping relationship.
Optionally, referring to fig. 7, in this embodiment, the method further includes the following steps:
step S310, when the front-end device 100 and the back-end device 200 are docked, detecting whether the interface fields of the front-end device 100 and the back-end device 200 are matched according to the field mapping.
Step S320, when the interface fields of the front-end device 100 and the back-end device 200 are not matched, the front-end device 100 modifies the data structure in the front-end configuration page.
In this embodiment, when the front-end device 100 and the back-end device 200 are docked, whether the interface fields of the two are matched is detected according to the mapping relationship between the two in the pre-established field mapping. If not, the data structure can be modified in the front-end configuration page without modifying each page of the front end one by one, so that the query modification time is reduced, and the development efficiency is improved.
With the above arrangement, the front-end device 100 can perform real service simulation development in a situation where the back-end development is not completed. The configuration file can be automatically generated by performing interface configuration on the front-end page through an interface engine simulation function developed by the back-end device 200. When the front-end device 100 and the back-end device 200 perform interface field docking, only the front-end configuration page needs to be modified when modification is required, and the interface field docking time is very short.
In addition, the interface engine can simulate a real server, so that various anomalies such as network anomaly, interface request time consumption, parameter incompatibilities with back-end requirements, cross-domain problems and the like can be simulated, and a web page which can deal with various anomalies and has good user experience can be developed under the condition that back-end development is not completed.
Referring to fig. 8, a functional module block diagram of the interface engine-based front-end and back-end development management system 10 according to the embodiment of the present application is shown. The interface engine-based front-end and back-end development management system 10 includes a front-end device 100 and a back-end device 200, where the front-end device 100 includes a first development management apparatus 110, the first development management apparatus 110 includes a configuration module 111 and an access module 112, the back-end device 200 includes a second development management apparatus 210, and the second development management apparatus 210 includes an interface template development module 211 and an interface access address generation module 212.
The interface template development module 211 is configured to develop an interface template for the back-end device 200, where the interface template may provide a configuration file format for the front-end device 100. The interface template development module 211 may be configured to execute step S110 shown in fig. 4, and the detailed description of step S110 may be referred to for a specific operation method.
The configuration module 111 is configured to configure configuration items according to the configuration file format, and store configuration information of each configuration item to generate a configuration file. The configuration module 111 can be used to execute step S120 shown in fig. 4, and the detailed description of step S120 can be referred to for a specific operation method.
The interface access address generating module 212 is configured to develop an interface engine, read configuration information of each configuration item in the configuration file through the interface engine, and dynamically generate an interface access address according to the configuration information. The interface access address generating module 212 may be configured to execute step S130 shown in fig. 4, and the detailed description of step S130 may be referred to for a specific operation method.
Optionally, referring to fig. 9, in the present embodiment, the interface access address generating module 212 includes a reading unit 2121 and a generating unit 2122.
The reading unit 2121 is configured to read, by the interface engine, configuration information of each configuration item in the configuration file by using a java reflection mechanism.
The generating unit 2122 is configured to initialize a database, insert configuration information of each configuration item into the database, and dynamically generate an interface access address according to the configuration information of each configuration item.
The access module 112 is configured to perform data access according to the interface access address. The access module 112 may be configured to execute step S140 shown in fig. 4, and the detailed description of step S140 may be referred to for a specific operation method.
Further, referring to fig. 10, in the present embodiment, the second development management apparatus 210 further includes a data structure obtaining module 213 and a field mapping generating module 214.
The data structure obtaining module 213 is configured to obtain a data structure simulated in a key-value pair form. The data structure obtaining module 213 may be configured to execute step S210 shown in fig. 6, and the detailed description of step S210 may be referred to for a specific operation method.
The field mapping generating module 214 is configured to utilize the interface engine to read the data structure according to the configuration information of each configuration item in the configuration file, and generate a corresponding field mapping according to the data structure for use by the front-end device 100, where the field mapping includes a mapping relationship between interface fields of the front-end device 100 and interface fields of the back-end device 200. The field mapping generating module 214 may be configured to execute step S220 shown in fig. 6, and the detailed description of step S220 may be referred to for a specific operation method.
In this embodiment, the interface engine includes a front-end configuration page, please refer to fig. 11, and the first development management apparatus 110 further includes a detection module 113 and a modification module 114.
The detection module 113 is configured to detect whether the interface fields of the front-end device 100 and the backend device 200 are matched according to the field mapping when the front-end device 100 and the backend device 200 are docked. The detection module 113 may be configured to perform step S310 shown in fig. 7, and the detailed description of step S310 may be referred to for a specific operation method.
The modification module 114 is configured to modify the data structure at the front-end configuration page when the interface fields of the front-end device 100 and the back-end device 200 do not match. The modification module 114 can be used to execute step S320 shown in fig. 7, and the detailed description of step S320 can be referred to for a specific operation method.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working process of the apparatus described above may refer to the corresponding process in the foregoing method, and will not be described in too much detail herein.
Through the above description of the embodiments, it is clear to those skilled in the art that the embodiments of the present invention may be implemented by hardware, or by software plus a necessary general hardware platform. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product, where the software product may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.), and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the implementation scenarios of the present application.
To sum up, according to the front-end and back-end development management method and system based on the interface engine provided in the embodiment of the present application, the back-end device 200 develops to obtain the interface template, and the front-end device 100 configures the configuration items according to the configuration file format included in the interface template, and stores and generates the configuration file. The back-end device 200 develops an interface engine, and reads configuration information of each configuration item in the configuration file through the interface engine to obtain an interface access address. The front-end device 100 performs data access according to the interface access address. According to the front-end and back-end development management scheme, the interface engine is obtained through development, the interface engine is utilized to read the configuration information of each configuration item in the configuration file, a data access interface is provided for the front-end equipment 100, the defect of a large amount of modification work during subsequent docking caused by simulated false data in the prior art is overcome, development is enabled to be more in line with requirements, data modification during subsequent docking can be reduced, and development efficiency is improved.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The apparatus embodiments described above are merely illustrative and, for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (10)
1. A front-end and back-end development management method based on an interface engine is characterized by comprising the following steps:
the back-end equipment develops to obtain an interface template, and the interface template can provide a configuration file format for the front-end equipment;
the front-end equipment configures configuration items according to the configuration file format and stores configuration information of each configuration item to generate a configuration file;
the back-end equipment develops an interface engine, reads the configuration information of each configuration item in the configuration file through the interface engine, and dynamically generates an interface access address according to the configuration information;
and the front-end equipment performs data access according to the interface access address.
2. The interface engine based front-end and back-end development management method of claim 1, further comprising:
the back-end equipment is designed to obtain a data structure simulated in a key value pair mode;
and reading the data structure by using the interface engine according to the configuration information of each configuration item in the configuration file, and generating a corresponding field mapping for the front-end equipment to use according to the data structure, wherein the field mapping comprises a mapping relation between an interface field of the front-end equipment and an interface field of the back-end equipment.
3. The interface engine based front-end and back-end development management method of claim 2, wherein the interface engine comprises a front-end configuration page, the method further comprising:
when the front-end equipment is in butt joint with the back-end equipment, whether the interface fields of the front-end equipment and the back-end equipment are matched or not is detected according to the field mapping;
and if not, the front-end equipment modifies the data structure on the front-end configuration page.
4. The interface engine-based front-end and back-end development management method according to claim 1, wherein the step of reading, by the interface engine, configuration information of each configuration item in the configuration file, and dynamically generating an interface access address according to the configuration information includes:
reading the configuration information of each configuration item in the configuration file by using a java reflection mechanism through the interface engine;
initializing a database, inserting the configuration information of each configuration item into the database, and dynamically generating an interface access address according to the configuration information of each configuration item.
5. The interface engine-based front-end and back-end development management method according to claim 1, wherein the step of configuring configuration items by the front-end device according to the configuration file format, and saving configuration information of each configuration item to generate a configuration file comprises:
the front-end equipment sends the request information of the configuration items to the back-end equipment through a request address according to the configuration file format;
after the request is successful, the back-end equipment feeds back response information corresponding to the request information to the front-end equipment;
and the front-end equipment completes the configuration of the configuration item according to the response information and stores the configuration information of the configuration item to generate a configuration file.
6. The interface engine-based front-end and back-end development management method according to claim 5, wherein the request information includes request parameters, request header information, and a request type, and the response information includes response data, response header information, and a response type.
7. A front-end equipment development management system based on an interface engine is characterized by comprising front-end equipment and back-end equipment which can establish communication connection, wherein the front-end equipment comprises a configuration module and an access module, and the back-end equipment comprises an interface template development module and an interface access address generation module;
the interface template development module is used for developing the back-end equipment to obtain an interface template, and the interface template can provide a configuration file format for the front-end equipment;
the configuration module is used for configuring configuration items according to the configuration file format and storing configuration information of each configuration item to generate a configuration file;
the interface access address generation module is used for developing an interface engine, reading the configuration information of each configuration item in the configuration file through the interface engine, and dynamically generating an interface access address according to the configuration information;
and the access module is used for accessing data according to the interface access address.
8. The interface engine based front-end and back-end device development management system of claim 7, wherein the back-end device further comprises a data structure acquisition module and a field mapping generation module;
the data structure acquisition module is used for designing and obtaining a data structure simulated in a key-value pair mode;
the field mapping generation module is configured to read the data structure by using the interface engine according to the configuration information of each configuration item in the configuration file, and generate a corresponding field mapping for the front-end device to use according to the data structure, where the field mapping includes a mapping relationship between an interface field of the front-end device and an interface field of the back-end device.
9. The interface engine based front-end and back-end device development management system of claim 8, wherein the interface engine comprises a front-end configuration page, the front-end device further comprises a detection module and a modification module;
the detection module is used for detecting whether the interface fields of the front-end equipment and the back-end equipment are matched according to the field mapping when the front-end equipment and the back-end equipment are in butt joint;
the modification module is used for modifying the data structure on the front-end configuration page when the interface fields of the front-end equipment and the back-end equipment are not matched.
10. The interface engine-based front-end and back-end device development management system of claim 7, wherein the interface access address generation module comprises a reading unit and a generation unit;
the reading unit is used for reading the configuration information of each configuration item in the configuration file by using a java reflection mechanism through the interface engine;
the generating unit is used for initializing a database, inserting the configuration information of each configuration item into the database, and dynamically generating an interface access address according to the configuration information of each configuration item.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810368902.9A CN108572823B (en) | 2018-04-23 | 2018-04-23 | Front-end and back-end development management method and system based on interface engine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810368902.9A CN108572823B (en) | 2018-04-23 | 2018-04-23 | Front-end and back-end development management method and system based on interface engine |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108572823A CN108572823A (en) | 2018-09-25 |
| CN108572823B true CN108572823B (en) | 2021-07-23 |
Family
ID=63575138
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810368902.9A Active CN108572823B (en) | 2018-04-23 | 2018-04-23 | Front-end and back-end development management method and system based on interface engine |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108572823B (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110826004A (en) * | 2019-11-05 | 2020-02-21 | 杭州安恒信息技术股份有限公司 | Front-end request data processing method and related device |
| CN111026394B (en) * | 2019-12-06 | 2020-12-15 | 光大兴陇信托有限责任公司 | Method for carrying out flow docking by utilizing self-service docking platform |
| CN111506298A (en) * | 2020-03-10 | 2020-08-07 | 南京行者易智能交通科技有限公司 | Method for carrying out interface visual configuration based on JSON object |
| CN111427568A (en) * | 2020-03-30 | 2020-07-17 | 山东浪潮通软信息科技有限公司 | Interface configuration method and device |
| CN111596902B (en) * | 2020-05-26 | 2023-03-28 | 牛津(海南)区块链研究院有限公司 | Method, device, equipment and storage medium for building front-end and back-end development framework |
| CN112052038B (en) * | 2020-09-09 | 2024-06-28 | 云账户技术(天津)有限公司 | Method and device for generating front-end interface |
| CN113254914A (en) * | 2021-04-24 | 2021-08-13 | 中电长城网际系统应用广东有限公司 | Front-end and back-end synchronous management method and system based on visual display |
| CN113282457B (en) * | 2021-05-25 | 2022-11-22 | 浪潮通用软件有限公司 | Method, device and medium for maintaining heterogeneous system integration interface information |
| CN113918129A (en) * | 2021-10-12 | 2022-01-11 | 城云科技（中国）有限公司 | Interface request processing method and device with front-end and back-end separation |
| CN114840765B (en) * | 2022-05-24 | 2025-04-15 | 中国平安财产保险股份有限公司 | Paging processing method, device, electronic device and storage medium |
| CN117331848B (en) * | 2023-12-01 | 2024-02-09 | 成都数之联科技股份有限公司 | Front-end and back-end development interaction method and system for Web mall |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101266666A (en) * | 1998-10-16 | 2008-09-17 | 开创网络有限公司 | Business documents in the trading partner network and interface definitions based on the documents |
| US8266601B2 (en) * | 2008-12-18 | 2012-09-11 | Microsoft Corporation | Framework for interoperability of solvers |
| CN106648556A (en) * | 2015-10-28 | 2017-05-10 | 北京国双科技有限公司 | Front end and back end integrated development testing method and device |
| CN106776345A (en) * | 2017-01-16 | 2017-05-31 | 北京恒华伟业科技股份有限公司 | A kind of interface delivery system and interface docking method of testing |
-
2018
- 2018-04-23 CN CN201810368902.9A patent/CN108572823B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101266666A (en) * | 1998-10-16 | 2008-09-17 | 开创网络有限公司 | Business documents in the trading partner network and interface definitions based on the documents |
| US8266601B2 (en) * | 2008-12-18 | 2012-09-11 | Microsoft Corporation | Framework for interoperability of solvers |
| CN106648556A (en) * | 2015-10-28 | 2017-05-10 | 北京国双科技有限公司 | Front end and back end integrated development testing method and device |
| CN106776345A (en) * | 2017-01-16 | 2017-05-31 | 北京恒华伟业科技股份有限公司 | A kind of interface delivery system and interface docking method of testing |
Non-Patent Citations (1)
| Title |
|---|
| 前端模拟后端接口返回数据常用的三种方法;刘挚珂;《https://www.jianshu.com/p/cb89d9ac635e》;20170523;第7-11页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108572823A (en) | 2018-09-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108572823B (en) | Front-end and back-end development management method and system based on interface engine | |
| US20180267885A1 (en) | Determining application test results using screenshot metadata | |
| US9208054B2 (en) | Web service for automated cross-browser compatibility checking of web applications | |
| CN110221959B (en) | Application program testing method, device and computer readable medium | |
| CN107729227B (en) | Application test scoping method, system, server and storage medium | |
| CN108427731A (en) | Processing method, device, terminal device and the medium of page code | |
| EP3161610B1 (en) | Optimized browser rendering process | |
| CN106648556B (en) | Method and device for front-end and back-end integrated development test | |
| JP6514244B2 (en) | Difference detection device and program | |
| CN110471657A (en) | The generation method and device of Website page | |
| CN106126410A (en) | The reminding method of code conflicts and device | |
| CN113448569A (en) | Site page processing system, method, equipment and storage medium | |
| CN108572911A (en) | Automate safety detecting method, device, electronic equipment and readable storage medium storing program for executing | |
| CN110955409A (en) | Method and device for creating resources on cloud platform | |
| CN110365776B (en) | Image batch download method, device, electronic device and storage medium | |
| CN112052157A (en) | Test message construction method, device and system | |
| EP3105691B1 (en) | Automatically embedding digital maps in software applications | |
| CN114579461A (en) | Browser compatibility detection method and related equipment | |
| CN106815010A (en) | A kind of method and device of operating database | |
| CN103019931A (en) | Method and device for detecting and treating Asn.1 interfaces | |
| CN114418120A (en) | Data processing method, device, equipment and storage medium of federal tree model | |
| CN118466986A (en) | Method, device, electronic equipment and computer readable storage medium for quick release of application | |
| CN114995790B (en) | A component development method, device, computer readable medium and electronic device | |
| CN112540747A (en) | Platform development method, device and computer readable storage medium | |
| CN111949510A (en) | Test processing method, apparatus, electronic device, and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240103 Address after: 310000, Building 4, 3rd Floor, Building C2, No. 590 Changhe Road, Changhe Street, Binjiang District, Hangzhou City, Zhejiang Province Patentee after: Hangzhou Tiansoft Technology Co.,Ltd. Address before: 11 / F, building B1, software industry phase 4.1, No.1, Software Park East Road, Donghu New Technology Development Zone, Wuhan City, Hubei Province, 430000 Patentee before: WUHAN DOUYU NETWORK TECHNOLOGY Co.,Ltd. |
|
| TR01 | Transfer of patent right |