CN113094195A - Interface calling file generation method and device - Google Patents
Interface calling file generation method and device Download PDFInfo
- Publication number
- CN113094195A CN113094195A CN202110489522.2A CN202110489522A CN113094195A CN 113094195 A CN113094195 A CN 113094195A CN 202110489522 A CN202110489522 A CN 202110489522A CN 113094195 A CN113094195 A CN 113094195A
- Authority
- CN
- China
- Prior art keywords
- request message
- node
- generating
- interface
- entity class
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to a method and a device for generating an interface calling file, which relate to the technical field of integrated interface development, and the method for generating the interface calling file comprises the following steps: responding to the calling instruction, and generating a Java entity class file according to the WebService interface request message XML; responding to the calling instruction, and generating a request message template file according to the WebService interface request message XML; and setting parameters of the Java entity class file, and generating an interface request message by combining the request message template file. According to the method and the device, the Java entity class file and the request message template file are generated based on the WebService interface request message XML, so that the interface request message is rapidly generated through parameter setting, and convenience is brought to interface calling work.
Description
Technical Field
The application relates to the technical field of integrated interface development, in particular to a method and a device for generating an interface calling file.
Background
With the development and maturity of informatization and related IT technologies, various information systems are introduced into a nuclear power plant, each system needs to interact with a third-party system under a specific use scene, for example, platform systems such as mails, OA (office automation) to-do, short messages and the like, most of functions realized by the third-party system are realized by calling a WebService interface, although the intranet is convenient to pass through a sopUI test interface, most information system developers develop functions in the extranet, and because the intranet and the extranet cannot be intercommunicated, client codes cannot be generated and called according to provided WebService description files through Axis, Cxf and other tool plugins in the extranet IDE.
To solve the above technical problems, a general interface calling file generation technology is provided to quickly and conveniently perform interface calling work
Disclosure of Invention
The application provides a method and a device for generating an interface calling file, which are used for generating a Java entity class file and a request message template file based on a WebService interface request message XML, so that the interface request message is quickly generated through parameter setting, and convenience is provided for interface calling work.
In a first aspect, the present application provides a method for generating an interface call file, where the method includes the following steps:
responding to the calling instruction, and generating a Java entity class file according to the WebService interface request message XML;
responding to a calling instruction, and generating a request message template file according to the WebService interface request message XML;
setting parameters of the Java entity class file, and generating an interface request message by combining the request message template file; wherein,
the Java entity class file comprises a plurality of parameter information, and the request message template file comprises the format of the interface request message and a plurality of parameter information corresponding to the Java entity class file.
Specifically, the generating of the Java entity class file according to the WebService interface request message XML includes the following steps:
analyzing each node in the WebService interface request message XML, polling each brother node and father-child node, and generating a character string attribute, an array object attribute and a parameter root object of a father node object according to a preset judgment condition.
Specifically, the determination conditions include:
judging nodes only containing text nodes as non-composite nodes, and generating character string attributes serving as father node objects;
generating object attributes which comprise child nodes and are non-repeatable nodes as parent node objects;
generating array object attributes by taking nodes which contain child nodes and are repeatable nodes as parent node objects;
the first and only node is generated as a parameter root object.
Further, the generating of the Java entity class file according to the WebService interface request message XML further includes the following steps:
and recursively polling each brother node and father-child node in the WebService interface request message XML, judging the nodes immediately after the annotation node as the repeat nodes, and storing the repeat nodes.
Further, the generating of the Java entity class file according to the WebService interface request message XML further includes the following steps:
and recursively polling each brother node and father-child node in the WebService interface request message XML, judging the corresponding node as a composite node when the child node of any node contains a non-text node, and storing the composite node.
Specifically, the generating of the request message template file according to the WebService interface request message XML includes the following steps:
recursively polling each brother node and each father node and each son node in the WebService interface request message XML;
setting the value of the non-composite node as an attribute placeholder corresponding to a parameter entity class;
adding a custom identifier before the node can be repeated, wherein the custom identifier is used as a positioning basis when carrying out array assignment and node dynamic expansion;
and adding a user authentication node.
Specifically, the parameter setting is performed on the Java entity class file, and an interface request message is generated by combining the request message template file, including the following steps:
the Java entity class file is instantiated, and parameter information of the Java entity class file required by a calling interface is set;
and combining the set parameter information of the Java entity class file with the request message template file to generate an interface request message.
Further, after generating the interface request message, the method further includes the following steps:
and sending the interface request message by using the http post.
Preferably, the interface request message is based on a SOAP protocol.
In a second aspect, the present application provides an apparatus for generating an interface call file, where the system includes:
the entity class file generating module is used for responding to the calling instruction and generating a Java entity class file according to the WebService interface request message XML;
the message template file generating module is used for responding to a response calling instruction and generating a request message template file according to the WebService interface request message XML;
an interface request message generation module, configured to perform parameter setting on the Java entity class file, and generate an interface request message in combination with the request message template file; wherein,
the Java entity class file comprises a plurality of parameter information, and the request message template file comprises the format of the interface request message and a plurality of parameter information corresponding to the Java entity class file.
The beneficial effect that technical scheme that this application provided brought includes:
according to the method and the device, the Java entity class file and the request message template file are generated based on the WebService interface request message XML, so that the interface request message is rapidly generated through parameter setting, and convenience is brought to interface calling work.
Drawings
Interpretation of terms:
XML: extensible Markup Language, also as a file format;
SOAP: simple Object Access Protocol, Simple Object Access Protocol;
WSDL: web Services Description Language, Web Services Description Language;
restful: a reproducible State Transfer, a design style and development mode of network applications;
the Freemarker is a template engine, a universal tool for generating text output based on a template and is written by pure Java;
office Automation (OA);
SoapUI: a tool for testing Web services;
IDE: integrated Development Environment, Integrated Development Environment;
axis: apache EXtensible Interaction System;
cxf: apache CXF — Celtix + XFire, an open source Services framework.
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flowchart illustrating steps of a method for generating an interface call file according to an embodiment of the present application;
fig. 2 is a block diagram of a structure of an interface call file generation apparatus provided in this embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
The embodiment of the application provides a method and a device for generating an interface calling file, wherein a Java entity class file and a request message template file are generated based on a WebService interface request message XML, so that the interface request message is quickly generated through parameter setting, and convenience is provided for interface calling work.
In order to achieve the technical effects, the general idea of the application is as follows:
a generation method of an interface call file comprises the following steps:
s1, responding to the call instruction, and generating a Java entity class file according to the WebService interface request message XML;
s2, responding to the call instruction, and generating a request message template file according to the WebService interface request message XML;
s3, setting parameters of the Java entity class file, and generating an interface request message by combining the request message template file; wherein,
the Java entity class file comprises a plurality of parameter information, and the request message template file comprises the format of the interface request message and a plurality of parameter information corresponding to the Java entity class file.
Embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
In a first aspect, referring to fig. 1, an embodiment of the present application provides a method for generating an interface call file, where the method includes the following steps:
s1, responding to the call instruction, and generating a Java entity class file according to the WebService interface request message XML;
s2, responding to the call instruction, and generating a request message template file according to the WebService interface request message XML;
s3, setting parameters of the Java entity files, and generating interface request messages by combining the template files of the request messages; wherein,
the Java entity class file comprises a plurality of parameter information, and the request message template file comprises a format of the interface request message and a plurality of parameter information corresponding to the Java entity class file.
In the embodiment of the application, the Java entity class file and the request message template file are generated based on the WebService interface request message XML, so that the interface request message is rapidly generated through parameter setting, and convenience is provided for interface calling work.
In the embodiment of the application, when the client code is specifically implemented, the client code generation is completed through the algorithm logic by using the SOAP protocol interface request message, and the call process of the SOAP protocol interface is completed in the current popular, lightweight and easily understood http post mode.
It should be noted that, due to the continuous development of technologies such as microservices and cloud computing, the interface calling method of the SOAP protocol has been gradually replaced by Restful, and tools capable of generating client codes for the SOAP protocol, such as Axis, Cxf and the like, on the market are old in version and not updated in time, and various limitations appear.
In general, compared with the prior art, the technical solution conceived by the embodiment of the present application can obtain the following gain effects:
(1) the original generated interface calls the client code, only existing framework tools in the industry can be adopted, the client code packet structure generated by the tools does not meet the project standard requirements, meanwhile, the XML description file has strict standard requirements, otherwise, the generation fails, meanwhile, communication with a server side is needed in the generation process of part of the interface client code to generate successfully, and the method in the embodiment of the application is inconvenient for deployment and development of internal and external networks respectively.
(2) The embodiment of the application has the advantages that the traditional WebService development is closer to the current popular Restful development, the log is popular and easy to understand, the understanding and troubleshooting of developers are easier, the WebService interface is simpler to develop under the current situation of development of an intranet in an extranet in the nuclear power field, and the WebService interface has stronger practicability.
Specifically, the method for generating the Java entity class file according to the WebService interface request message XML comprises the following steps:
analyzing each node in the WebService interface request message XML, polling each brother node and father-child node, and generating a character string attribute, an array object attribute and a parameter root object of a father node object according to a preset judgment condition.
Specifically, the determination conditions include:
judging nodes only containing text nodes as non-composite nodes, and generating character string attributes serving as father node objects;
generating object attributes which comprise child nodes and are non-repeatable nodes as parent node objects;
generating array object attributes by taking nodes which contain child nodes and are repeatable nodes as parent node objects;
the first and only node is generated as a parameter root object.
Further, in generating the Java entity class file according to the WebService interface request message XML, the method further includes the following steps:
and recursively polling each brother node and each father-child node in the WebService interface request message XML, judging the nodes immediately after the annotation nodes as the repeat nodes, and storing the repeat nodes.
Further, in generating the Java entity class file according to the WebService interface request message XML, the method further includes the following steps:
and recursively polling each brother node and each father and child node in the WebService interface request message XML, judging the corresponding node as a composite node when the child node of any node contains a non-text node, and storing the composite node.
Specifically, the method for generating the request message template file according to the WebService interface request message XML includes the following steps:
recursively polling each brother node and each father node and each son node in the WebService interface request message XML;
setting and grouping the values of the non-composite nodes as attribute placeholders corresponding to the parameter entity classes;
adding a custom identifier before the node can be repeated, wherein the custom identifier is used as a positioning basis when carrying out array assignment and node dynamic expansion;
and adding a user authentication node.
Specifically, the method for setting parameters of the Java entity class file and generating the interface request message by combining the request message template file includes the following steps:
the Java entity class file is instantiated, and parameter information of the Java entity class file required by a calling interface is set;
and combining the set parameter information of the Java entity class file with the request message template file to generate an interface request message.
Further, after generating the interface request message, the method further comprises the following steps:
and sending an interface request message by using the http post.
It should be noted that the interface request message is based on the SOAP protocol.
It should be noted that the working principle of the embodiment of the present application is as follows:
a set of algorithm logic is customized to generate a java entity class according to a WebService description XML file, a request message template is generated at the same time, attributes of the entity class correspond to placeholders in the request message template one by one, interface calling parameter values are set for java entity objects when an interface is called, then the java entity objects are combined with the request message template to generate a correct WebService request message, and finally the request message is sent to a short message server by using a post method of httpClient to realize a short message sending function;
it should be noted that the request message template file may specifically be a Freemarker template file.
Specifically, the embodiment of the present application, when implemented specifically, includes the following steps:
q1, generating a java entity file according to the WebService interface request message XML;
q2, generating a request message template file according to the WebService interface request message XML;
q3, instantiating a java entity file, setting parameters, combining with the request message template file to generate a complete interface request message, and sending the complete interface request message to the platform system through the http post to complete interface calling.
Wherein, in the step Q1, the method specifically comprises the following steps:
q101, recursively polling the brother nodes and the father and son nodes in the WebService interface request message XML, if encountering an annotation node, saving the nodes immediately after the annotation node as repeatable nodes, which is similar to <! The comment of-Zero or more repetition of-xsd 1: CreateWorkOrder > </xsd1: CreateWorkOrder > is a comment node;
q102, recursively polling the WebService interface request message XML each brother node and father node, if the child node of a certain node contains a non-text node, saving the node as a compound node, wherein the node is similar to CreateWorkOrder in < xsd1: CreateWorkOrder > < xsd1: Businesssobject > </xsd1: Businesssossobject > </xsd1: CreateWorkOrder >;
q103, analyzing nodes in the request message XML of the WebService interface, continuously polling sibling nodes and father and child nodes, if a non-composite node is encountered, namely a node only containing a text node, generating character string attributes of a father node object, if a node is encountered, the node contains a child node and is a non-repeatable node, generating object attributes of the father node object, if the node contains a child node and is a repeatable node, generating array object attributes of the father node object, finally generating the first and only child node under body as a parameter root object, and finally successfully generating all parameter object entity classes.
Wherein, in the step Q2, the method specifically comprises the following steps:
q201, recursively polling the brother nodes and the father and son nodes in the WebService interface request message XML, if a non-composite node is encountered, setting the value of the node as an attribute placeholder corresponding to a parameter entity class, similarly $ { (sms. if _ exists }.
Q202, recursively polling each brother node and father node in the WebService interface request message XML, if a repeatable node is encountered, adding Freemarker identifiers < # assign n, < # if and < # list in front of the node, and conveniently performing array assignment and node dynamic expansion when the message is assembled.
Q203, adding a user authentication node for the request message XML of the WebService interface, and adding a wsse security verification part, namely adding a child node < wsse: Userna meToken > under the < Header > node.
Wherein, in the step Q3, the method specifically comprises the following steps:
q301, instantiating the entity class generated in the step Q1 in the program, and setting parameters required by the call interface;
q302, combining the instantiated parameter object with a Freemarker request message template to generate a complete request message;
and Q303, sending the generated request message to an interface provider system by using an http post method to complete interface calling.
In order to make the objects, technical solutions and advantages of the embodiments of the present application more clearly apparent, the following detailed description is made with reference to table 1. It should be understood that the specific examples described herein are intended to illustrate but not limit the embodiments of the disclosure.
TABLE 1
In a second aspect, referring to fig. 2, an embodiment of the present application provides an apparatus for generating an interface call file, where the apparatus is based on the method for generating an interface call file mentioned in the first aspect, and the system includes:
the entity class file generating module is used for responding to the calling instruction and generating a Java entity class file according to the WebService interface request message XML;
the message template file generating module is used for responding to the response calling instruction and generating a request message template file according to the WebService interface request message XML;
the interface request message generation module is used for setting parameters of the Java entity class file and generating an interface request message by combining the request message template file; wherein,
the Java entity class file comprises a plurality of parameter information, and the request message template file comprises a format of the interface request message and a plurality of parameter information corresponding to the Java entity class file.
In the embodiment of the application, the Java entity class file and the request message template file are generated based on the WebService interface request message XML, so that the interface request message is rapidly generated through parameter setting, and convenience is provided for interface calling work.
In the embodiment of the application, when the client code is specifically implemented, the client code generation is completed through the algorithm logic by using the SOAP protocol interface request message, and the call process of the SOAP protocol interface is completed in the current popular, lightweight and easily understood http post mode.
It should be noted that, due to the continuous development of technologies such as microservices and cloud computing, the interface calling method of the SOAP protocol has been gradually replaced by Restful, and tools capable of generating client codes for the SOAP protocol, such as Axis, Cxf and the like, on the market are old in version and not updated in time, and various limitations appear.
In general, compared with the prior art, the technical solution conceived by the embodiment of the present application can obtain the following gain effects:
(1) the original generated interface calls the client code, only existing framework tools in the industry can be adopted, the client code packet structure generated by the tools does not meet the project standard requirements, meanwhile, the XML description file has strict standard requirements, otherwise, the generation fails, meanwhile, communication with a server side is needed in the generation process of part of the interface client code to generate successfully, and the method in the embodiment of the application is inconvenient for deployment and development of internal and external networks respectively.
(2) The embodiment of the application has the advantages that the traditional WebService development is closer to the current popular Restful development, the log is popular and easy to understand, the understanding and troubleshooting of developers are easier, the WebService interface is simpler to develop under the current situation of development of an intranet in an extranet in the nuclear power field, and the WebService interface has stronger practicability.
Specifically, the entity class file generating module generates the Java entity class file according to the WebService interface request message XML, and includes the following steps:
analyzing each node in the WebService interface request message XML, polling each brother node and father-child node, and generating a character string attribute, an array object attribute and a parameter root object of a father node object according to a preset judgment condition.
Specifically, the determination conditions include:
judging nodes only containing text nodes as non-composite nodes, and generating character string attributes serving as father node objects;
generating object attributes which comprise child nodes and are non-repeatable nodes as parent node objects;
generating array object attributes by taking nodes which contain child nodes and are repeatable nodes as parent node objects;
the first and only node is generated as a parameter root object.
Further, the entity class file generating module, in generating the Java entity class file according to the WebService interface request message XML, further includes the following steps:
and recursively polling each brother node and each father-child node in the WebService interface request message XML, judging the nodes immediately after the annotation nodes as the repeat nodes, and storing the repeat nodes.
Further, the entity class file generating module, in generating the Java entity class file according to the WebService interface request message XML, further includes the following steps:
and recursively polling each brother node and each father and child node in the WebService interface request message XML, judging the corresponding node as a composite node when the child node of any node contains a non-text node, and storing the composite node.
Specifically, the message template file generating module generates the request message template file according to the WebService interface request message XML, and includes the following steps:
recursively polling each brother node and each father node and each son node in the WebService interface request message XML;
setting and grouping the values of the non-composite nodes as attribute placeholders corresponding to the parameter entity classes;
adding a custom identifier before the node can be repeated, wherein the custom identifier is used as a positioning basis when carrying out array assignment and node dynamic expansion;
and adding a user authentication node.
Specifically, the interface request message generating module performs parameter setting on the Java entity class file, and generates the interface request message by combining the request message template file, including the following steps:
the Java entity class file is instantiated, and parameter information of the Java entity class file required by a calling interface is set;
and combining the set parameter information of the Java entity class file with the request message template file to generate an interface request message.
Further, the device also comprises an interface request message sending module, which is used for sending the interface request message by using http post after the interface request message is generated.
It should be noted that the interface request message is based on the SOAP protocol.
It should be noted that the working principle of the embodiment of the present application is as follows:
a set of algorithm logic is customized to generate a java entity class according to a WebService description XML file, a request message template is generated at the same time, attributes of the entity class correspond to placeholders in the request message template one by one, interface calling parameter values are set for java entity objects when an interface is called, then the java entity objects are combined with the request message template to generate a correct WebService request message, and finally the request message is sent to a short message server by using a post method of httpClient to realize a short message sending function;
it should be noted that the request message template file may specifically be a Freemarker template file.
It is noted that, in the present application, relational terms such as "first" and "second", and the like, are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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 foregoing are merely exemplary embodiments of the present application and are presented to enable those skilled in the art to understand and practice the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for generating an interface call file is characterized by comprising the following steps:
responding to the calling instruction, and generating a Java entity class file according to the WebService interface request message XML;
responding to a calling instruction, and generating a request message template file according to the WebService interface request message XML;
setting parameters of the Java entity class file, and generating an interface request message by combining the request message template file; wherein,
the Java entity class file comprises a plurality of parameter information, and the request message template file comprises the format of the interface request message and a plurality of parameter information corresponding to the Java entity class file.
2. The method for generating an interface call file according to claim 1, wherein the step of generating a Java entity class file according to the WebService interface request message XML comprises the steps of:
analyzing each node in the WebService interface request message XML, polling each brother node and father-child node, and generating a character string attribute, an array object attribute and a parameter root object of a father node object according to a preset judgment condition.
3. The generation method of an interface call file according to claim 2, wherein the determination condition includes:
judging nodes only containing text nodes as non-composite nodes, and generating character string attributes serving as father node objects;
generating object attributes which comprise child nodes and are non-repeatable nodes as parent node objects;
generating array object attributes by taking nodes which contain child nodes and are repeatable nodes as parent node objects;
the first and only node is generated as a parameter root object.
4. The method for generating an interface call file according to claim 2, wherein the step of generating a Java entity class file according to the WebService interface request message XML further comprises the steps of:
and recursively polling each brother node and father-child node in the WebService interface request message XML, judging the nodes immediately after the annotation node as the repeat nodes, and storing the repeat nodes.
5. The method for generating an interface call file according to claim 2, wherein the step of generating a Java entity class file according to the WebService interface request message XML further comprises the steps of:
and recursively polling each brother node and father-child node in the WebService interface request message XML, judging the corresponding node as a composite node when the child node of any node contains a non-text node, and storing the composite node.
6. The method for generating an interface call file according to claim 3, wherein the step of generating a request message template file according to the WebService interface request message XML comprises the steps of:
recursively polling each brother node and each father node and each son node in the WebService interface request message XML;
setting the value of the non-composite node as an attribute placeholder corresponding to a parameter entity class;
adding a custom identifier before the node can be repeated, wherein the custom identifier is used as a positioning basis when carrying out array assignment and node dynamic expansion;
and adding a user authentication node.
7. The method for generating an interface call file according to claim 1, wherein the parameter setting is performed on the Java entity class file, and an interface request packet is generated in combination with the request packet template file, and the method comprises the following steps:
the Java entity class file is instantiated, and parameter information of the Java entity class file required by a calling interface is set;
and combining the set parameter information of the Java entity class file with the request message template file to generate an interface request message.
8. The method for generating an interface call file according to claim 1, wherein after generating the interface request message, the method further comprises the steps of:
and sending the interface request message by using the http post.
9. The generation method of an interface call file according to claim 1, characterized in that:
the interface request message is based on the SOAP protocol.
10. An apparatus for generating an interface call file, the apparatus comprising:
the entity class file generating module is used for responding to the calling instruction and generating a Java entity class file according to the WebService interface request message XML;
the message template file generating module is used for responding to a response calling instruction and generating a request message template file according to the WebService interface request message XML;
an interface request message generation module, configured to perform parameter setting on the Java entity class file, and generate an interface request message in combination with the request message template file; wherein,
the Java entity class file comprises a plurality of parameter information, and the request message template file comprises the format of the interface request message and a plurality of parameter information corresponding to the Java entity class file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110489522.2A CN113094195B (en) | 2021-04-30 | 2021-04-30 | Method and device for generating interface calling file |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110489522.2A CN113094195B (en) | 2021-04-30 | 2021-04-30 | Method and device for generating interface calling file |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113094195A true CN113094195A (en) | 2021-07-09 |
| CN113094195B CN113094195B (en) | 2024-09-24 |
Family
ID=76681716
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110489522.2A Active CN113094195B (en) | 2021-04-30 | 2021-04-30 | Method and device for generating interface calling file |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113094195B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115242631A (en) * | 2022-08-01 | 2022-10-25 | 中电金信软件有限公司 | Message processing method and device, electronic equipment and storage medium |
| CN115952321A (en) * | 2022-12-05 | 2023-04-11 | 中信银行股份有限公司 | Method and system for realizing XML (extensive makeup language) Schema interface |
| CN116016625A (en) * | 2022-12-26 | 2023-04-25 | 中科云谷科技有限公司 | Calling method, device, computer equipment and storage medium of WebService interface |
| CN120743288A (en) * | 2025-08-15 | 2025-10-03 | 浪潮通用软件有限公司 | WSDL-based server API automatic construction method, equipment and medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030182395A1 (en) * | 2002-03-21 | 2003-09-25 | International Business Machines Corporation | Interfacing objects and markup language messages |
| US20040015840A1 (en) * | 2001-04-19 | 2004-01-22 | Avaya, Inc. | Mechanism for converting between JAVA classes and XML |
| US20060031233A1 (en) * | 2004-08-06 | 2006-02-09 | Oracle International Corporation | Technique of using XMLType tree as the type infrastructure for XML |
| CN101771701A (en) * | 2010-01-04 | 2010-07-07 | 北京航空航天大学 | Web service client automation generation method and device |
| CN105488014A (en) * | 2015-11-27 | 2016-04-13 | 中国民生银行股份有限公司 | Generating method and device of interface test case message in XML format |
| CN107391153A (en) * | 2017-07-31 | 2017-11-24 | 深圳乐信软件技术有限公司 | A code generation method and device based on the integration of Spring and MyBatis framework |
| CN110187878A (en) * | 2019-05-29 | 2019-08-30 | 北京三快在线科技有限公司 | A kind of page generation method and device |
| CN110333847A (en) * | 2019-05-07 | 2019-10-15 | 重庆天蓬网络有限公司 | A kind of integrated approach that back end interface automatic document generates |
-
2021
- 2021-04-30 CN CN202110489522.2A patent/CN113094195B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040015840A1 (en) * | 2001-04-19 | 2004-01-22 | Avaya, Inc. | Mechanism for converting between JAVA classes and XML |
| US20030182395A1 (en) * | 2002-03-21 | 2003-09-25 | International Business Machines Corporation | Interfacing objects and markup language messages |
| US20060031233A1 (en) * | 2004-08-06 | 2006-02-09 | Oracle International Corporation | Technique of using XMLType tree as the type infrastructure for XML |
| CN101771701A (en) * | 2010-01-04 | 2010-07-07 | 北京航空航天大学 | Web service client automation generation method and device |
| CN105488014A (en) * | 2015-11-27 | 2016-04-13 | 中国民生银行股份有限公司 | Generating method and device of interface test case message in XML format |
| CN107391153A (en) * | 2017-07-31 | 2017-11-24 | 深圳乐信软件技术有限公司 | A code generation method and device based on the integration of Spring and MyBatis framework |
| CN110333847A (en) * | 2019-05-07 | 2019-10-15 | 重庆天蓬网络有限公司 | A kind of integrated approach that back end interface automatic document generates |
| CN110187878A (en) * | 2019-05-29 | 2019-08-30 | 北京三快在线科技有限公司 | A kind of page generation method and device |
Non-Patent Citations (3)
| Title |
|---|
| HERON V. O. SILVA ET AL.: "NCL 2.0: integrating new concepts to XML modular languages", 《DOCENG \'04: PROCEEDINGS OF THE 2004 ACM SYMPOSIUM ON DOCUMENT ENGINEERING》, 28 October 2004 (2004-10-28), pages 188 - 197 * |
| 曹洪其等: "基于XML数据的频繁模式挖掘算法", 《计算机应用研究》, 31 December 2007 (2007-12-31), pages 116 - 119 * |
| 郭宏燕等: "基于WebService的状态监测系统I2接口研究与实现", 《电器与能效管理技术》, no. 3, pages 153 - 156 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115242631A (en) * | 2022-08-01 | 2022-10-25 | 中电金信软件有限公司 | Message processing method and device, electronic equipment and storage medium |
| CN115242631B (en) * | 2022-08-01 | 2023-10-13 | 中电金信软件有限公司 | Message processing method and device, electronic equipment and storage medium |
| CN115952321A (en) * | 2022-12-05 | 2023-04-11 | 中信银行股份有限公司 | Method and system for realizing XML (extensive makeup language) Schema interface |
| CN116016625A (en) * | 2022-12-26 | 2023-04-25 | 中科云谷科技有限公司 | Calling method, device, computer equipment and storage medium of WebService interface |
| CN120743288A (en) * | 2025-08-15 | 2025-10-03 | 浪潮通用软件有限公司 | WSDL-based server API automatic construction method, equipment and medium |
| CN120743288B (en) * | 2025-08-15 | 2026-02-17 | 浪潮通用软件有限公司 | Methods, equipment, and media for automatically building server-side APIs based on WSDL |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113094195B (en) | 2024-09-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113094195B (en) | Method and device for generating interface calling file | |
| CN112748908B (en) | Method and device for developing Restful service based on SSM framework | |
| CN111290753B (en) | Method, device, equipment and storage medium for building front-end development environment | |
| CN110674027B (en) | SDN data plane software conformance testing system and method for P4 programming language | |
| US10678682B2 (en) | Intelligent batch job testing | |
| CN111736813B (en) | JPA code generation method and device, terminal equipment and storage medium | |
| CN108984155B (en) | Data processing flow setting method and device | |
| CN118034673B (en) | Visual editing generation and dynamic analysis system for equipment model of Internet of things | |
| CN112507005B (en) | Method and device for processing message | |
| CN110874278B (en) | Embedding methods, workflow systems, devices, and storage media of external systems | |
| CN113157904B (en) | Sensitive word filtering method and system based on DFA algorithm | |
| CN111767096A (en) | Method, apparatus, device and computer-readable storage medium for generating interface document | |
| Klinbua et al. | Translating tosca into docker-compose yaml file using antlr | |
| CN111580797B (en) | A method of dynamic routing grouping based on dubbo and spring framework | |
| CN102055623A (en) | Method and system for automatically testing embedded type browser | |
| Masood et al. | An automated approach to regression testing of web services based on WSDL operation changes | |
| CN117271465A (en) | A log generation method, device, equipment and storage medium | |
| CN117170684A (en) | File compiling method, device, equipment and storage medium | |
| CN113805875A (en) | Cross-language code automatic generation platform | |
| CN113704382A (en) | Text matching method and device | |
| CN119987941B (en) | A method for cross-platform instruction set interoperability based on finite state machines | |
| CN120892030B (en) | Method and apparatus for editing seismic batch processing jobs using scripting languages | |
| CN115878344A (en) | Data processing method, device, medium and equipment based on protobuf | |
| CN114995915A (en) | Template configuration method, device, electronic device and storage medium | |
| EP1581869A2 (en) | A method and system for dynamically creating parsers in a message broker |
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 |