CN114168149A

CN114168149A - Data conversion method and device

Info

Publication number: CN114168149A
Application number: CN202111499245.XA
Authority: CN
Inventors: 刘坤; 李检全; 李建峰; 李毅
Original assignee: WeBank Co Ltd
Current assignee: WeBank Co Ltd
Priority date: 2021-12-09
Filing date: 2021-12-09
Publication date: 2022-03-11
Also published as: WO2023103339A1

Abstract

The invention discloses a data conversion method and a device, wherein the method comprises the following steps: reading XML data to be converted to obtain a first file object; analyzing the first file object to obtain first user-defined Map structure data; the first custom Map structure data comprises a key value determined based on the node path and the node characteristics and a value corresponding to the key value; determining attribute annotation information of a user-defined Java object corresponding to the first file object, and determining a mapping key value corresponding to the user-defined Java object based on the attribute annotation information; and searching a matching value matched with the mapping key value in the first custom Map structure data, reflecting and assigning the matching value to the custom JAVA object, and obtaining the target Java object. When the method is applied to financial technology (Fintech), the conversion efficiency of the conversion between XML data and Java objects is improved.

Description

Data conversion method and device

Technical Field

The embodiment of the invention relates to the field of financial technology (Fintech), in particular to a data conversion method and device.

Background

With the development of computer technology, more and more technologies are applied in the financial field, and the traditional financial industry is gradually changing to financial technology, but due to the requirements of the financial industry on safety and real-time performance, higher requirements are also put forward on the technologies.

Currently, in the financial industry, each member institution performs message communication with a ticket exchange to realize the whole transaction flow of the electronic commercial draft. As can be seen, the message parsing is the basic message data of the whole transaction flow processing. Because the message is in XML format, and the message has many kinds and deep hierarchy, how to parse the message into Java objects used by the system and convert the processed Java objects into XML format data becomes a problem to be solved urgently.

In view of this, solutions are provided in the related art, which utilize a Java parsing component to parse XML data into related data objects, and then convert the data objects into customized Java objects. However, with this scheme, when the format of the XML data is not fixed, the parsing mapping relationship needs to be determined again for each type of XML data. Therefore, the mapping analysis mode provided in the related technology has poor expansibility, which results in low conversion efficiency of XML data and Java objects, and further influences the processing efficiency of the transaction flow.

Disclosure of Invention

The invention provides a data conversion method and a data conversion device, which are used for solving the problem of low conversion efficiency of XML data and Java objects in the prior art.

In a first aspect, the present invention provides a data conversion method, including: reading XML data to be converted to obtain a first file object; analyzing the first file object to obtain first user-defined Map structure data; the first custom Map structure data comprises a key value determined based on a node path and a node characteristic and a value corresponding to the key value; determining attribute annotation information of a user-defined Java object corresponding to the first file object, and determining a mapping key value corresponding to the user-defined Java object based on the attribute annotation information; and searching a matching value matched with the mapping key value in the first custom Map structure data, reflecting and assigning the matching value to the custom JAVA object, and obtaining a target Java object corresponding to the XML data to be converted.

In the method, the conversion from the XML data to the Java object is automatically completed through the first self-defined Map structure data, the attribute annotation information, the reflection and other modes, and the data conversion efficiency is improved.

Optionally, after obtaining the target Java object corresponding to the XML data to be converted, the method further includes: obtaining a new Java object after the operation of the target Java object; obtaining annotation attribute information corresponding to the new Java object through reflection processing of the new Java object, and storing path information and data in the annotation attribute information into second self-defined Map structure data; creating a second file object, and finishing the establishment of an object tree corresponding to the second file object based on the path information and the data in the second self-defined Map structure data; and performing reverse analysis processing on the object tree through a preset plug-in to generate target XML data corresponding to the new Java object.

In the method, based on the second custom Map structure data and the preset plug-in, conversion from the Java object to XML data is realized, and the data conversion efficiency is improved.

Optionally, the establishing of the object tree corresponding to the second file object is completed based on the path information and the data in the second custom Map structure data, including: determining a root node corresponding to the path information in the second custom Map structure data; analyzing each path information in the second custom Map structure data based on a preset analysis rule, respectively obtaining a corresponding father path and a corresponding son path, taking a node corresponding to the son path as a son node, and determining a value corresponding to the son node; when the corresponding information of the parent path is not a distinguisher, determining whether the root node comprises the node corresponding to the parent path; when determining that the root node comprises the node corresponding to the parent path, taking the node corresponding to the parent path as a child node, and determining a value corresponding to the child node; when determining that the root node does not comprise the node corresponding to the parent path, taking the node corresponding to the parent path as the parent node, and determining a value corresponding to the parent node; when the corresponding information of the parent path is a distinguisher, determining that the node corresponding to the parent path is an attribute node, and the data value corresponding to the parent path is a corresponding value; and constructing an object tree corresponding to the second file object based on the parent node, the child node and the attribute node and the value values respectively corresponding to the parent node, the child node and the attribute node.

Based on the method, the XML data can be converted into the self-defined rule in the Java object, namely the corresponding relation between the path information and the node, the Element object tree is reversely constructed, and the conversion between the new Java object and the target XML data is quickly realized.

Optionally, analyzing the first file object to obtain first user-defined Map structure data includes: analyzing the first file object to obtain a root node and a child node of the root node of the first file object; and traversing the child nodes of the root node, and determining key values corresponding to the child nodes and value values corresponding to the key values so as to determine first user-defined Map structural data.

Based on the method, the embodiment of the invention provides the first self-defined Map structure data, and a passing conversion mode can be provided for XML data with different formats based on the Map structure data, namely, a newly-built Java object only needs to inherit the Map structure data to realize the mutual conversion of the Java object and the XML without other analysis type components, so that the data conversion efficiency is improved.

Optionally, traversing the child nodes of the root node, and determining a key value corresponding to each child node and a value corresponding to the key value to determine first custom Map structure data, including: when any child node is determined to be an attribute node, adding any child node to the first custom Map structure data, and determining that a key value corresponding to any child node comprises a root path, a node name, a distinguishing character and an attribute name, and a value corresponding to the key value is an attribute value; when any child node is determined to be a leaf node and no key value exists in the first custom Map structural data, adding any child node to the first custom Map structural data, determining that the key value corresponding to any child node comprises a root path and a node name, and determining that a value corresponding to the key value is a node data value; when any child node is determined to be a leaf node and a key value exists in the first custom Map structural data, any child node is added to the first custom Map structural data, the key value corresponding to any child node is determined to comprise a root path, a node name and a subscript distinguishing symbol, and the value corresponding to the key value is determined to be a node data value.

Based on the method, a scheme for recursively converting the first file object into the Map structure data is provided, and based on the scheme, the efficiency of converting XML data in different formats into intermediate variables, namely Map structure data can be accelerated.

Optionally, determining a mapping key value corresponding to the custom Java object based on the attribute annotation information includes: when it is determined that the homonymous node information does not exist in the attribute annotation information and XML attribute information does not exist in the attribute annotation information, determining that the mapping key value comprises a path; when it is determined that the homonymous node information exists in the attribute annotation information and the XML attribute information does not exist in the attribute annotation information, determining that the mapping key value comprises a path and a homonymous node sequence number in a preset format; when it is determined that the same-name node information does not exist in the attribute annotation information and XML attribute information exists in the attribute annotation information, determining that the mapping key value comprises a path, a distinguisher and an attribute name; and when the same-name node information exists in the attribute annotation information and the XML attribute information exists in the attribute annotation information, determining that the mapping key value comprises a path, a distinguisher, an attribute name and a subscript distinguisher.

Based on the method, the attribute annotation information can mark the position of the XML data to which the attribute of the Java object is mapped, namely, the mapping is marked by the path in the annotation, thereby realizing the self-defined path mapping. That is, the attributes of the Java-supported objects are mapped to the attributes of the nodes in the XML data by the custom-designed path mapping rules.

Optionally, the attribute annotation information corresponding to the custom Java object is updated based on the XML data to be converted.

Based on the method, the XML data with different formats can correspond to different annotations, so that the mutual conversion between the XML data and the JAVA object can be realized more quickly, and the conversion efficiency of the data is improved.

In a second aspect, the present invention provides a data conversion apparatus, including: the first obtaining unit is used for reading XML data to be converted to obtain a first file object; the first processing unit is used for analyzing the first file object to obtain first user-defined Map structure data; the first custom Map structure data comprises a key value determined based on a node path and a node characteristic and a value corresponding to the key value; the second processing unit is used for determining attribute annotation information of a custom Java object corresponding to the first file object and determining a mapping key value corresponding to the custom Java object based on the attribute annotation information; and the second obtaining unit is used for searching a matching value matched with the mapping key value in the first self-defined Map structure data, reflecting and assigning the matching value to the self-defined JAVA object, and obtaining a target Java object corresponding to the XML data to be converted.

Optionally, the apparatus further includes a third processing unit, configured to: obtaining a new Java object after the operation of the target Java object; obtaining annotation attribute information corresponding to the new Java object through reflection processing of the new Java object, and storing path information and data in the annotation attribute information into second self-defined Map structure data; creating a second file object, and finishing the establishment of an object tree corresponding to the second file object based on the path information and the data in the second self-defined Map structure data; and performing reverse analysis processing on the object tree through a preset plug-in to generate target XML data corresponding to the new Java object.

Optionally, the third processing unit is specifically configured to: based on the path information and data in the second custom Map structure data, completing establishment of an object tree corresponding to the second file object, including: determining a root node corresponding to the path information in the second custom Map structure data; analyzing each path information in the second custom Map structure data based on a preset analysis rule, respectively obtaining a corresponding father path and a corresponding son path, taking a node corresponding to the son path as a son node, and determining a value corresponding to the son node; when the corresponding information of the parent path is not a distinguisher, determining whether the root node comprises the node corresponding to the parent path; when determining that the root node comprises the node corresponding to the parent path, taking the node corresponding to the parent path as a child node, and determining a value corresponding to the child node; when determining that the root node does not comprise the node corresponding to the parent path, taking the node corresponding to the parent path as the parent node, and determining a value corresponding to the parent node; when the corresponding information of the parent path is a distinguisher, determining that the node corresponding to the parent path is an attribute node, and the data value corresponding to the parent path is a corresponding value; and constructing an object tree corresponding to the second file object based on the parent node, the child node and the attribute node and the value values respectively corresponding to the parent node, the child node and the attribute node.

Optionally, the first processing unit is specifically configured to: analyzing the first file object to obtain a root node and a child node of the root node of the first file object; and traversing the child nodes of the root node, and determining key values corresponding to the child nodes and value values corresponding to the key values so as to determine first user-defined Map structural data.

Optionally, the first processing unit is specifically configured to: when any child node is determined to be an attribute node, adding any child node to the first custom Map structure data, and determining that a key value corresponding to any child node comprises a root path, a node name, a distinguishing character and an attribute name, and a value corresponding to the key value is an attribute value; when any child node is determined to be a leaf node and no key value exists in the first custom Map structural data, adding any child node to the first custom Map structural data, determining that the key value corresponding to any child node comprises a root path and a node name, and determining that a value corresponding to the key value is a node data value; when any child node is determined to be a leaf node and a key value exists in the first custom Map structural data, any child node is added to the first custom Map structural data, the key value corresponding to any child node is determined to comprise a root path, a node name and a subscript distinguishing symbol, and the value corresponding to the key value is determined to be a node data value.

Optionally, the second processing unit is configured to: when it is determined that the homonymous node information does not exist in the attribute annotation information and XML attribute information does not exist in the attribute annotation information, determining that the mapping key value comprises a path; when it is determined that the homonymous node information exists in the attribute annotation information and the XML attribute information does not exist in the attribute annotation information, determining that the mapping key value comprises a path and a homonymous node sequence number in a preset format; when it is determined that the same-name node information does not exist in the attribute annotation information and XML attribute information exists in the attribute annotation information, determining that the mapping key value comprises a path, a distinguisher and an attribute name; and when the same-name node information exists in the attribute annotation information and the XML attribute information exists in the attribute annotation information, determining that the mapping key value comprises a path, a distinguisher, an attribute name and a subscript distinguisher.

The advantageous effects of the second aspect and the various optional apparatuses of the second aspect may refer to the advantageous effects of the first aspect and the various optional methods of the first aspect, and are not described herein again.

In a third aspect, the present invention provides a computer device comprising a program or instructions for performing the method of the first aspect and the alternatives of the first aspect when the program or instructions are executed.

In a fourth aspect, the present invention provides a storage medium comprising a program or instructions which, when executed, is adapted to perform the method of the first aspect and the alternatives of the first aspect.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that are required to be used in the description of the embodiments will be briefly described below.

FIG. 1 is a schematic diagram of a prior art method for providing data conversion;

fig. 2 is a schematic diagram of an application scenario provided in an embodiment of the present invention;

FIG. 3 is a flowchart illustrating steps of a data conversion method according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of a path provided by an embodiment of the present invention;

FIG. 5 is a diagram illustrating attribute annotation information provided by an embodiment of the invention;

FIG. 6 is a diagram illustrating XML data converted into Java objects according to an embodiment of the present invention;

FIG. 7 is a diagram illustrating a Java object converted into XML data according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of a data conversion apparatus according to an embodiment of the present invention.

Detailed Description

In order to better understand the technical solutions, the technical solutions will be described in detail below with reference to the drawings and the specific embodiments of the specification, and it should be understood that the embodiments and specific features of the embodiments of the present invention are detailed descriptions of the technical solutions of the present invention, and are not limitations of the technical solutions of the present invention, and the technical features of the embodiments and examples of the present invention may be combined with each other without conflict.

It is noted that the terms first, second and the like in the description and in the claims of the present invention are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the images so used are interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.

In order to facilitate understanding of the technical solutions provided by the embodiments of the present invention, some key terms used in the embodiments of the present invention are explained first:

1. XML: is a subset of the markup language, extensible markup language, standard universal markup language, used to mark electronic documents to make them structural.

2. DOM, SAX, JDOM, DOM 4J: DOM and SAX are ways in which Java sources generate support for XML data parsing, and JDOM and DOM4J are open source components implemented to simplify Java and XML interactions. Specifically, DOM4J related to the present invention is an XML API of Java, which is an upgrade of JDOM, and is used for reading and writing XML files.

3. FasterXML: the FasterXML jackson-database is a JAVA-based library that can convert data formats such as XML and JSON into JAVA objects. Jackson can easily convert Java objects into json objects and XML documents, and also can convert json and XML into Java objects.

4. Document file object: DOM4J component is a Java object generated when reading and writing XML files.

5. Element object: in the Document object, analyzing each XML data node into an Element object; the whole Element object is of a tree structure, and the root node of the Element object is a root node in XML data. Specifically, the root node can be obtained using the get RootElement method of the Document object, and the entire Element object tree is traversed in this way.

6. Path: the path in the implementation of the present invention refers to a path from a root node to a data node in XML data.

7. And annotating: the support for metadata in Java language, annotation is special mark in code, and these mark can be read in compiling, class loading, runtime, and execute corresponding processing.

The following briefly introduces the design concept of the embodiment of the present invention:

currently, in the financial industry, each member institution performs message communication with a ticket exchange to realize the whole transaction flow of the electronic commercial draft. Because the message is in XML format, and the message has many kinds and deep hierarchy, how to parse the message into Java objects used by the system and convert the processed Java objects into XML format data becomes a problem to be solved urgently.

In response to the problem, solutions are provided in the related art, which can utilize Java parsing components, such as DOM, SAX, JDOM, DOM4J, etc., to parse XML data into related data objects, and then convert the data objects into custom Java objects. However, when the XML data format is not fixed, each XML data needs a handwriting parsing mapping process, i.e. the hard parsing scheme has poor extensibility, resulting in low conversion efficiency between the XML data and the Java object, and further affecting the processing efficiency of the transaction flow.

Furthermore, the related art also provides that the existing open source component, such as FasterXML, can be utilized to analyze and complete the mapping of XML data and Java objects. However, in this scheme, each XML data needs to generate a corresponding Java object, and when the XML node hierarchy is deep, the data objects are complex and have security holes.

For example, referring to fig. 1, wherein a in fig. 1 is XML data, B in fig. 1 is a Java object corresponding to the XML data, wherein the Java object has four layers in hierarchy, and the nesting inside the a object defines 3 internal classes, it is obvious that when field assignment is performed on the a object, the code is very bloated. Moreover, the open source component, especially the analysis component, has more security holes and higher risk of strictly depending on the subsequent maintenance of the open source component program.

In view of this, the present invention provides a data conversion method, by which a data mapping relationship between a Document object and a custom Java object can be completed through a self-design rule data intermediate layer Map, and the parsing mapping of XML data and Java objects is realized.

After the design concept of the embodiment of the present invention is introduced, some simple descriptions are made below on application scenarios to which the data conversion technical solution in the embodiment of the present invention is applicable, and it should be noted that the application scenarios described in the embodiment of the present invention are for more clearly describing the technical solution in the embodiment of the present invention, and do not form a limitation on the technical solution provided in the embodiment of the present invention.

In the embodiment of the present invention, please refer to the schematic application scenario shown in fig. 2, where the scenario includes an electronic device 201 and a computer device 202, and the electronic device 201 may communicate with the computer device 202, for example, directly or indirectly connect through a wired or wireless communication manner, which is not limited in the present invention.

In this scenario, the electronic device 201 may send XML data to the computer device 202, and the computer device 202 performs conversion processing on the XML data to obtain a corresponding Java object, and feeds the Java object back to the electronic device 201.

The computer device 202 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a Network service, cloud communication, a middleware service, a domain name service, a security service, a CDN (Content Delivery Network), a big data and artificial intelligence platform, and the like. The electronic device 201 may be a smartphone, a tablet computer, a laptop computer, a desktop computer, a smart television, a smart wearable device, etc., or may be a server, but is not limited thereto.

To further illustrate the scheme of the data conversion method provided by the embodiment of the present invention, the following detailed description is made with reference to the accompanying drawings and the specific embodiments. Although embodiments of the present invention provide method steps as shown in the following embodiments or figures, more or fewer steps may be included in the method based on conventional or non-inventive efforts. In steps where no necessary causal relationship exists logically, the order of execution of the steps is not limited to that provided by embodiments of the present invention. The method can be executed in sequence or in parallel according to the method shown in the embodiment or the figures when the method is executed in an actual processing procedure or a device (for example, a parallel processor or an application environment of multi-thread processing).

The data conversion method in the embodiment of the present invention is described below with reference to the method flowchart shown in fig. 3, and the method flow in the embodiment of the present invention is described below.

Step 301: and reading XML data to be converted to obtain a first file object.

In the embodiment of the present invention, the electronic device may send the XML data to be converted to the computer device, and then the computer device may read the XML data to be converted based on the preset parsing component, so as to obtain the Document object (i.e., the first file object). Wherein the preset parsing component may be DOM 4J.

Step 302: analyzing the first file object to obtain first user-defined Map structure data; the first custom Map structure data includes a key value determined based on the node path and the node characteristic and a value corresponding to the key value.

In the embodiment of the present invention, after obtaining the first file object, the computer device may parse the first file, so as to obtain the first custom Map structure data.

In the embodiment of the present invention, the following steps may be adopted, but not limited to, to determine the first custom Map structure data:

step A: and analyzing the first file object to obtain a root node and a child node of the root node of the first file object.

In the embodiment of the present invention, the computer device performs depth-first traversal on the first file object, recursively obtains the root node root of the Document object and all child nodes child of the root node root, and may further determine a path of the child node, where the path is a path determined based on a custom rule.

For example, referring to fig. 4, fig. 4 is a schematic diagram of a path according to an embodiment of the present invention. Specifically, each path from the root node a to each child node is referred to as an XML path, and hereinafter referred to as a root path. In addition, the path separators in the embodiment of the invention use English periods for separation. As shown in fig. 4, the path of the AB child node is: A.AB; and the node path of the AAC child node is as follows: aa.aaa.aac. In addition, the node without a child node (i.e., degree 0) in fig. 4 is referred to as a leaf node, e.g., child node AAAA, and the last-level child node AAA and child node AAA in fig. 4 are homonymous nodes.

And B: and traversing the child nodes of the root node, and determining key values corresponding to the child nodes and value values corresponding to the key values so as to determine the first self-defined Map structure data.

In the embodiment of the present invention, when it is determined that any child node is an attribute node, any child node is added to the first custom Map structure data, and it is determined that a key value corresponding to any child node includes a root path, a node name, a specifier, and an attribute name, and a value corresponding to the key value is an attribute value.

For example, when child node 1 is determined to be an attribute node, the attribute node is added to the first custom Map structure data, and the key value corresponding to child node 1 may be represented as: the root path + this node name + < attr > + attribute name, such as a.aa. < attr >. name, and the value corresponding to the key value is the attribute value corresponding to child node 1.

In the embodiment of the invention, when any child node is determined to be a leaf node and no key value exists in the first custom Map structural data of any child node, any child node is added to the first custom Map structural data, and the key value corresponding to any child node is determined to comprise a root path and a node name, and the value corresponding to the key value is determined to be a node data value.

For example, when the child node 2 is a leaf node and the child node 2 is added to the first custom Map structure data, the key value corresponding to the child node 2 may be represented as: root path + this node name, e.g., a.aa, and the value to which the key value corresponds is this node data value.

In addition, when any child node is determined to be a non-leaf node, the root node is returned to perform recursive processing, and the root path is set as a current path corresponding to any child node to perform traversal processing.

In the embodiment of the present invention, when it is determined that any child node is a leaf node and a key value exists in the first custom Map structure data in any child node, any child node is added to the first custom Map structure data, and it is determined that the key value corresponding to any child node includes a root path, a node name, and a subscript difference, and a value corresponding to the key value is a node data value.

For example, when the child node 3 is a leaf node and the child node 3 has a key value in the first custom Map structure data, the child node 3 is added to the first custom Map structure data, and the key value corresponding to the child node 3 can be expressed as: the root path + the node name, and index the key value, such as a.aa [1], and the value corresponding to the key value is the node data value.

In the embodiment of the invention, when all the subnodes are processed, the key value and the value corresponding to each node are added into the first custom Map structure to obtain the first custom Map structure data.

Step 303: and determining attribute annotation information of the custom Java object corresponding to the first file object, and determining a mapping key value corresponding to the custom Java object based on the attribute annotation information.

In the embodiment of the present invention, the computer device may further determine attribute annotation information of the custom Java object corresponding to the first file object. The attribute annotation information comprises path information, homonymous node information and XML attribute information.

Referring to fig. 5, fig. 5 is a schematic diagram of exemplary attribute annotation information according to an embodiment of the present invention. Therein, WeXML in fig. 5 may be understood as attribute annotation information, which includes path, index, and isAttr. Specifically, the path is an XML node path (e.g., a.aa.aaa.aaac), index is a subscript of a node with the same name, default is 0 (node without the same name), isAttr is whether an XML attribute is present, and default is no.

Therefore, in the embodiment of the invention, the attribute annotation information can mark the position of the XML data to which the attribute of the Java object is mapped, namely, the position is marked by the path in the annotation, thereby realizing the self-defined path mapping. That is, the attributes of the Java-supported objects are mapped to the attributes of the nodes in the XML data by the custom-designed path mapping rules. And the problem that XML data allows nodes with the same name to exist but the attributes in the Java object cannot be renamed can be solved through the attribute annotation information, namely, a scheme that a set of available annotation information is mapped into keys in Map is designed in the embodiment of the invention.

In the embodiment of the present invention, the mapping key value may be determined correspondingly in the following ways:

mode 1:

in the embodiment of the invention, when the same-name node information does not exist in the attribute annotation information and the XML attribute information does not exist in the attribute annotation information, the mapping key value is determined to comprise the path.

For example, path information in the attribute annotation information is determined, and if index is equal to 0 and isAttr is false, the mapping key value is equal to path.

Mode 2:

in the embodiment of the invention, when the homonymous node information exists in the attribute annotation information and the XML attribute information does not exist in the attribute annotation information, the mapping key value is determined to comprise a path and a homonymous node sequence number in a preset format.

For example, path information in the attribute annotation information is determined, and if index is greater than 0 and isAttr is false, the mapped key value is equal to path + [ index ], such as A.AA [1 ].

Mode 3:

in the embodiment of the invention, when it is determined that the same-name node information does not exist in the attribute annotation information and the XML attribute information exists in the attribute annotation information, it is determined that the mapping key value includes a path, a distinguisher and an attribute name.

For example, path information in the attribute annotation information is determined, and if index is equal to 0 and isAttr is true, the mapping key value is equal to path + < attr > + attribute name, for example, a.aa. < attr >. name.

Mode 4:

and when the same-name node information exists in the attribute annotation information and the XML attribute information exists in the attribute annotation information, determining that the mapping key value comprises a path, a distinguisher, an attribute name and a subscript distinguisher.

For example, determining path information in the attribute annotation information, if index is greater than 0 and isAttr is true, then mapping key is equal to path + < attr > + attribute name [ index ], for example, mapping key value is: A.AA. < attr >. name [1 ].

Step 304: and searching a matching value matched with the mapping key value in the first custom Map structure data, reflecting and assigning the matching value to the custom JAVA object, and obtaining a target Java object corresponding to the XML data to be converted.

In the embodiment of the invention, only the Java object corresponding to the XML needs to be defined, the whole mapping and analyzing process is automatically completed, and the efficiency of converting XML data of different formats into the Java object is greatly improved.

Optionally, the attribute annotation information corresponding to the custom Java object is updated based on the XML data to be converted. Therefore, in the embodiment of the invention, the computer equipment can analyze the attributes of the Java objects into the custom annotation of the XML, namely, the position of the XML data to which the attributes of the Java objects are mapped is determined, and the position is marked by the path in the annotation, so that the custom path mapping is realized. In addition, the corresponding attribute annotation information is different according to the different format of the XML data.

Referring to fig. 6, fig. 6 is a schematic diagram illustrating an embodiment of the present invention for converting XML data into Java objects. The parser may perform depth-first traversal of all element nodes and save path information from the root node to the leaf nodes. Illustratively, the path information is divided by english periods, i.e., small dots. And the Key value in the first custom structure Map data is Document node path, and the value is node data information. In addition, the mapper can analyze the attribute annotation information of the custom Java object, then obtain a corresponding value according to a path in the attribute annotation information, and finally assign the corresponding value to the Java object through reflection processing to obtain the target Java object.

Therefore, through a series of self-defined analysis mapping rules and self-defined Map structure data, and through Java annotation, reflection and other modes, the generation of XML data to Java objects and data injection are automatically completed.

In the embodiment of the invention, after the computer equipment obtains the target Java object, the computer equipment can also operate on the target Java object so as to obtain a new Java object. It should be noted that the operation processing on the target Java object may be determined based on actual implementation correspondence, which is not limited in the embodiment of the present invention.

In the embodiment of the invention, the computer equipment can acquire annotation attribute information corresponding to the new Java object by performing reflection processing on the new Java object, and store path information and data in the annotation attribute information into second self-defined Map structure data. Further, the computer device may create a second file object, and complete the establishment of the object tree corresponding to the second file object based on the path information and data in the second custom Map structure data. Then, the computer device can perform reverse analysis processing on the object tree through a preset plug-in to generate target XML data corresponding to the new Java object.

For example, in the process of completing the building of the object tree corresponding to the second file object, the following steps may be adopted, but are not limited to:

step a: and circularly traversing the second user-defined Map structure data to acquire the path information of the root node and the child node.

In the embodiment of the present invention, the root node may be set as root, and then the path information whose path is equal to the key value in the second custom Map structure data is obtained, so that the path information is analyzed to determine the parent node and the child node.

The preset analysis rule may intercept a path from 0 to the first delimiter in the path information as a parent path; and setting the path from the first separator to the path information tail as a sub-path. Hereinafter, the parent path may be referred to as "ppath" and the child path may be referred to as "cpath".

For example, assume that the path information is: aa.aaa path, it can be determined that a is ppath and aa.aaa is cpath.

Specifically, a node corresponding to the ppath can be searched or generated under the root node. And if the root node has a node corresponding to the ppath, taking the current ppath node as a child node, taking the path information as cpath, and determining the value corresponding to the node. And if the root node has no node corresponding to the ppath, newly building the node corresponding to the ppath, wherein the node corresponding to the ppath is a parent node, and determining the value corresponding to the node.

Optionally, when the ppath is < attr >, that is, the information corresponding to the parent path is a distinguisher, the attribute name of the current node may be set to be cpath, and the data value corresponding to the node is value. That is, the current node is an attribute node.

Step b: and after traversing all the data of the second custom Map structure data, generating the Element object tree with root as the root node.

In the embodiment of the invention, when no path exists under each cpath, the root node, the leaf node and the non-leaf node are all generated at the time, so that the Element object tree is obtained.

Therefore, if the path information has a parent node, the node is set behind the parent node, namely mounted under the parent node, and if the path information does not have the parent node, the child node in the path information is determined as the parent node, so that when traversing of data in the second custom Map structure data is completed, namely when analyzing all path information is completed, the corresponding Element object tree can be obtained.

Referring to fig. 7, fig. 7 is a schematic diagram of a new Java object to be converted as target XML data according to an embodiment of the present invention. The object parser is used for parsing all fields and values of the Java object and path information in a field (for example, called as @ WeXML) corresponding to the attribute annotation information, and then storing the path information and the values into the second custom Map structure data. Therefore, the key value in the second custom Map structure data is data path information, and the value is data information. Further, the node generator may traverse the second custom Map structure data, and then recursively generate a tree node, i.e., an element object, according to the path information, i.e., the key value, so as to fill the data value in the second custom Map structure data into the corresponding leaf node, and fill the attribute information into the corresponding node attribute information, thereby filling the whole node data into the newly-created second file object, i.e., the Document object. Thus, the target XML data can be obtained.

Therefore, in the embodiment of the invention, the Element object tree can be reversely constructed by converting the XML data into the self-defined rule in the Java object, so that the Element object tree is analyzed to obtain new XML data. Obviously, the data conversion scheme provided by the embodiment of the invention can realize the mutual conversion of XML data in various formats and Java objects.

In order to better describe the conversion process when the XML data and the Java object are converted into each other and the node attribute or the node with the same name exists in the XML data, a specific example is described below.

Specifically, when there is a node attribute in the XML data, such as:

<AB>

<AAAAname＝"test">aaaa</AAAA>

</AB>

when XML is analyzed to be the first self-defined Map structure data in the forward direction, the XML is automatically mapped to the following data:

1.key＝AB.AAAA.<attr>.name,value＝test；

2.key＝AB.AAAA,value＝aaaa；

therefore, in the object reverse analysis value searching, the key value in the first custom Map structure data in the automatic searching is as follows: data information of ab.aaaa. < attr >. name and ab.aaaa.

Specifically, for the first custom Map structure data, the key value includes path information, and the key in the first custom Map structure data is unique. However, in XML data, homonym nodes are allowed to exist. For this problem, in the forward XML parsing, array subscripts are automatically added, such as: A.AA.AAA.AAAB [0] and A.AA.AAA.AAAB [1], etc.

For the Java object, index needs to be specified in the annotation, so in the Java object reverse parsing value searching, the key value in the first custom Map structure data is automatically found to be: data information of A.AA.AAA.AAAB [0] and A.AA.AAA.AAAB [1 ].

As shown in fig. 8, the present invention provides a data conversion apparatus, including: a first obtaining unit 801, configured to read XML data to be converted to obtain a first file object; a first processing unit 802, configured to parse the first file object to obtain first user-defined Map structure data; the first custom Map structure data comprises a key value determined based on a node path and a node characteristic and a value corresponding to the key value; the second processing unit 803 is configured to determine attribute annotation information of a custom Java object corresponding to the first file object, and determine, based on the attribute annotation information, a mapping key value corresponding to the custom Java object; a second obtaining unit 804, configured to search for a matching value that is matched with the mapping key value in the first custom Map structure data, reflect and assign the matching value to the custom JAVA object, and obtain a target JAVA object corresponding to the XML data to be converted.

Optionally, the first processing unit 802 is specifically configured to: analyzing the first file object to obtain a root node and a child node of the root node of the first file object; and traversing the child nodes of the root node, and determining key values corresponding to the child nodes and value values corresponding to the key values so as to determine first user-defined Map structural data.

Optionally, the first processing unit 802 is specifically configured to: when any child node is determined to be an attribute node, adding any child node to the first custom Map structure data, and determining that a key value corresponding to any child node comprises a root path, a node name, a distinguishing character and an attribute name, and a value corresponding to the key value is an attribute value; when any child node is determined to be a leaf node and no key value exists in the first custom Map structural data, adding any child node to the first custom Map structural data, determining that the key value corresponding to any child node comprises a root path and a node name, and determining that a value corresponding to the key value is a node data value; when any child node is determined to be a leaf node and a key value exists in the first custom Map structural data, any child node is added to the first custom Map structural data, the key value corresponding to any child node is determined to comprise a root path, a node name and a subscript distinguishing symbol, and the value corresponding to the key value is determined to be a node data value.

Optionally, the second processing unit 803 is configured to: when it is determined that the homonymous node information does not exist in the attribute annotation information and XML attribute information does not exist in the attribute annotation information, determining that the mapping key value comprises a path; when it is determined that the homonymous node information exists in the attribute annotation information and the XML attribute information does not exist in the attribute annotation information, determining that the mapping key value comprises a path and a homonymous node sequence number in a preset format; when it is determined that the same-name node information does not exist in the attribute annotation information and XML attribute information exists in the attribute annotation information, determining that the mapping key value comprises a path, a distinguisher and an attribute name; and when the same-name node information exists in the attribute annotation information and the XML attribute information exists in the attribute annotation information, determining that the mapping key value comprises a path, a distinguisher, an attribute name and a subscript distinguisher.

Embodiments of the present invention provide a computer device, which includes a program or an instruction, and when the program or the instruction is executed, the computer device is configured to execute a data conversion method and any optional method provided by embodiments of the present invention.

Embodiments of the present invention provide a storage medium, which includes a program or an instruction, and when the program or the instruction is executed, the storage medium is configured to execute a data conversion method and any optional method provided by embodiments of the present invention.

Finally, it should be noted that: as will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims

1. A method of data conversion, comprising:

reading XML data to be converted to obtain a first file object;

analyzing the first file object to obtain first user-defined Map structure data; the first custom Map structure data comprises a key value determined based on a node path and a node characteristic and a value corresponding to the key value;

determining attribute annotation information of a user-defined Java object corresponding to the first file object, and determining a mapping key value corresponding to the user-defined Java object based on the attribute annotation information;

and searching a matching value matched with the mapping key value in the first custom Map structure data, reflecting and assigning the matching value to the custom JAVA object, and obtaining a target Java object corresponding to the XML data to be converted.

2. The method of claim 1, wherein after obtaining the target Java object corresponding to the XML data to be converted, the method further comprises:

obtaining a new Java object after the operation of the target Java object;

obtaining annotation attribute information corresponding to the new Java object through reflection processing of the new Java object, and storing path information and data in the annotation attribute information into second self-defined Map structure data;

creating a second file object, and finishing the establishment of an object tree corresponding to the second file object based on the path information and the data in the second self-defined Map structure data;

and performing reverse analysis processing on the object tree through a preset plug-in to generate target XML data corresponding to the new Java object.

3. The method of claim 2, wherein completing the building of the object tree corresponding to the second file object based on the path information and data in the second custom Map structure data comprises:

determining a root node corresponding to the path information in the second custom Map structure data;

analyzing each path information in the second custom Map structure data based on a preset analysis rule, respectively obtaining a corresponding father path and a corresponding son path, taking a node corresponding to the son path as a son node, and determining a value corresponding to the son node;

when the corresponding information of the parent path is not a distinguisher, determining whether the root node comprises the node corresponding to the parent path;

when determining that the root node comprises the node corresponding to the parent path, taking the node corresponding to the parent path as a child node, and determining a value corresponding to the child node; when determining that the root node does not comprise the node corresponding to the parent path, taking the node corresponding to the parent path as the parent node, and determining a value corresponding to the parent node;

when the corresponding information of the parent path is a distinguisher, determining that the node corresponding to the parent path is an attribute node, and the data value corresponding to the parent path is a corresponding value;

and constructing an object tree corresponding to the second file object based on the parent node, the child node and the attribute node and the value values respectively corresponding to the parent node, the child node and the attribute node.

4. The method of claim 1, wherein parsing the first file object to obtain first custom Map structure data comprises:

analyzing the first file object to obtain a root node and a child node of the root node of the first file object;

and traversing the child nodes of the root node, and determining key values corresponding to the child nodes and value values corresponding to the key values so as to determine first user-defined Map structural data.

5. The method of claim 4, wherein traversing the children of the root node, determining a key value corresponding to each child node and a value corresponding to the key value, to determine first custom Map structure data, comprises:

when any child node is determined to be an attribute node, adding any child node to the first custom Map structure data, and determining that a key value corresponding to any child node comprises a root path, a node name, a distinguishing character and an attribute name, and a value corresponding to the key value is an attribute value;

when any child node is determined to be a leaf node and no key value exists in the first custom Map structural data, adding any child node to the first custom Map structural data, determining that the key value corresponding to any child node comprises a root path and a node name, and determining that a value corresponding to the key value is a node data value;

when any child node is determined to be a leaf node and a key value exists in the first custom Map structural data, any child node is added to the first custom Map structural data, the key value corresponding to any child node is determined to comprise a root path, a node name and a subscript distinguishing symbol, and the value corresponding to the key value is determined to be a node data value.

6. The method of claim 1, wherein determining the mapping key value corresponding to the custom Java object based on the attribute annotation information comprises:

when it is determined that the homonymous node information does not exist in the attribute annotation information and XML attribute information does not exist in the attribute annotation information, determining that the mapping key value comprises a path;

when it is determined that the homonymous node information exists in the attribute annotation information and the XML attribute information does not exist in the attribute annotation information, determining that the mapping key value comprises a path and a homonymous node sequence number in a preset format;

when it is determined that the same-name node information does not exist in the attribute annotation information and XML attribute information exists in the attribute annotation information, determining that the mapping key value comprises a path, a distinguisher and an attribute name;

7. The method according to any one of claims 1 to 6, wherein the attribute annotation information corresponding to the custom Java object is updated based on the XML data to be converted.

8. A data conversion apparatus, comprising:

the first obtaining unit is used for reading XML data to be converted to obtain a first file object;

the first processing unit is used for analyzing the first file object to obtain first user-defined Map structure data; the first custom Map structure data comprises a key value determined based on a node path and a node characteristic and a value corresponding to the key value;

the second processing unit is used for determining attribute annotation information of a custom Java object corresponding to the first file object and determining a mapping key value corresponding to the custom Java object based on the attribute annotation information;

and the second obtaining unit is used for searching a matching value matched with the mapping key value in the first self-defined Map structure data, reflecting and assigning the matching value to the self-defined JAVA object, and obtaining a target Java object corresponding to the XML data to be converted.

9. A computer device comprising a program or instructions that, when executed, perform the method of any of claims 1 to 6.

10. A storage medium comprising a program or instructions which, when executed, perform the method of any one of claims 1 to 6.