CN113110847B - Conversion processing method and system for program codes - Google Patents
Conversion processing method and system for program codes Download PDFInfo
- Publication number
- CN113110847B CN113110847B CN202110476837.3A CN202110476837A CN113110847B CN 113110847 B CN113110847 B CN 113110847B CN 202110476837 A CN202110476837 A CN 202110476837A CN 113110847 B CN113110847 B CN 113110847B
- Authority
- CN
- China
- Prior art keywords
- conversion
- data transmission
- entity class
- receiving
- calling
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000006243 chemical reaction Methods 0.000 title claims abstract description 166
- 238000003672 processing method Methods 0.000 title claims abstract description 19
- 230000005540 biological transmission Effects 0.000 claims abstract description 111
- 238000000034 method Methods 0.000 claims description 17
- 238000012545 processing Methods 0.000 claims description 14
- 238000000586 desensitisation Methods 0.000 claims description 5
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000013461 design Methods 0.000 description 6
- 238000012546 transfer Methods 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 3
- 235000010627 Phaseolus vulgaris Nutrition 0.000 description 2
- 244000046052 Phaseolus vulgaris Species 0.000 description 2
- 239000011800 void material Substances 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 235000015170 shellfish Nutrition 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
- 230000014616 translation Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention provides a conversion processing method of program codes, which comprises the following steps: establishing a conversion relation between the entity class object and the data transmission object; designating a conversion direction; acquiring a receiving object corresponding to the conversion direction; identifying the receiving object to obtain a calling code of the receiving object; converting the call codes of the received objects into call codes of the target objects according to the conversion directions and the conversion relations; when the receiving object is an entity class object, the target object is a data transmission object; when the receiving object is a data transmission object, the target object is an entity class object. The beneficial effects are that: the logical binding of the entity class object and the data transmission object is realized, and the mutual conversion between the entity class object and the data transmission object is realized through the conversion relation.
Description
Technical Field
The present invention relates to the field of computer software technologies, and in particular, to a method and a system for converting and processing program codes.
Background
The current back-end development is especially in the technical architecture based on Java Spring system. Domain-Driving Design (Domain-Driving Design) is a Design concept that is widely recognized in the industry. The main idea is that the data structure of each service interface carrying data fully characterizes its service. However, in relational database design, database entity classes often follow the database design paradigm specification, focusing on underlying data relationships, avoiding excessive redundancy. The entity class is not very intuitive for the business description in some scenarios if it is a domain object, and therefore it is necessary to convert the entity class object into a data transfer object required for the interface.
In the service design, entity class objects and data transmission objects have high consistency in fields described in a large number of service fields; however, the entity class object contains all the information of the service data, and the data transmission object only contains the necessary information in the service data.
The prior art can directly convert the data transmission object into the entity class object, but a large number of extremely high code reproducibility exists in the converted code in the prior art, and the repeated use of writing once cannot be realized for business processing. Moreover, when other interfaces also need to acquire user related information but service data needs are different, the above-mentioned prior art cannot be reused simply.
The prior art can also use common objects to deeply copy shellfish libraries, such as org.apache.common.beans.beans, but the prior art has the following problems:
firstly, default only supports field depth copy of the same name and the same type, and conversion of different names and different types cannot be processed;
secondly, the processing is carried out in a reflection mode, so that the performance is poor;
thirdly, when the converted field is eliminated, a field name in the form of a character string needs to be provided, and if the entity class object or the data transmission object field is modified, the problem cannot be found through grammar inspection;
fourth, the business conversion processing such as the amount of orders, the amount of orders and the like cannot be performed;
fifth, if the persistence method of JPA such as Hibernate is used, lazy loading with relation definition will be triggered continuously during deep copying, resulting in crash.
Disclosure of Invention
In order to solve the above problems in the prior art, a method and a system for converting program codes are provided.
The specific technical scheme is as follows:
a conversion processing method of program codes, comprising the steps of:
establishing a conversion relation between the entity class object and the data transmission object;
designating a conversion direction;
acquiring a receiving object corresponding to the conversion direction;
identifying the receiving object to obtain a calling code of the receiving object;
converting the call codes of the received objects into call codes of the target objects according to the conversion directions and the conversion relations;
when the receiving object is an entity class object, the target object is a data transmission object;
when the receiving object is a data transmission object, the target object is an entity class object.
Preferably, the conversion processing method of the program code, wherein, the conversion relation between the entity class object and the data transmission object is established, specifically comprises the following steps:
establishing a conversion relation between the entity class object and the calling codes corresponding to the homonymous fields in the data transmission object;
establishing a conversion relation between the entity class object and the call codes corresponding to the same field data in the data transmission object;
establishing a conversion relation between the entity class object and the call codes corresponding to the similar remarks in the data transmission object;
and establishing a conversion relation between the entity class object and the call codes with association relation in the data transmission object.
Preferably, the method for converting and processing program codes, wherein the conversion relation between the entity class object and the data transmission object is created through the syntax tree structure of the APT.
Preferably, the conversion processing method of the program code, after establishing the conversion relation between the entity class object and the data transmission object, further includes:
triggering alarm information when the calling code of the entity class object is changed; or (b)
When the calling code of the data transmission object changes, the alarm information is triggered.
Preferably, the program code conversion processing method, wherein when the receiving object includes a call code corresponding to the privacy data;
and performing desensitization processing on the privacy data so as to prevent the privacy data in the receiving object from being revealed through the call code of the target object obtained after conversion after the conversion relation between the entity class object and the data transmission object is established.
Preferably, the program code conversion processing method, wherein the conversion direction includes:
converting the entity class object into a data transmission object; and
converting the data transmission object into an entity class object;
one of them.
Preferably, the program code is converted and processed, wherein the data transmission object is a DTO object.
There is also provided a conversion processing system of program codes, including:
the relation determining module comprises a conversion relation between the entity class object and the data transmission object;
the direction determining module is used for designating a conversion direction;
the receiving module is used for acquiring a receiving object corresponding to the conversion direction;
the recognition module is used for converting the calling codes of the received objects into the calling codes of the target objects according to the conversion direction and the conversion relation;
the conversion module is used for converting the calling code of the receiving object into the calling code of the target object by adopting the converter according to the conversion direction;
when the receiving object is an entity class object, the target object is a data transmission object;
when the receiving object is a data transmission object, the target object is an entity class object.
There is also provided a computer-readable storage medium having stored thereon a calling program executable on a processor, the calling program, when executed by the processor, implementing a program code conversion processing method according to any one of the above.
The technical scheme has the following advantages or beneficial effects:
the conversion relation between the entity class object and the data transmission object is established, namely the logic binding between the entity class object and the data transmission object is realized at one time, so that the subsequent conversion between the entity class object and the data transmission object is realized directly through the conversion relation;
avoiding leaking privacy data acquired by calling codes in a second object code after the entity class object is converted into the data transmission object by setting the conversion direction;
and the mutual conversion of the entity class object and the data transmission object is realized by setting the conversion direction and creating the conversion relation.
Drawings
Embodiments of the present invention will now be described more fully with reference to the accompanying drawings. The drawings, however, are for illustration and description only and are not intended as a definition of the limits of the invention.
FIG. 1 is a flowchart of a method for converting program code according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be noted that, without conflict, the embodiments of the present invention and features of the embodiments may be combined with each other.
The invention is further described below with reference to the drawings and specific examples, which are not intended to be limiting.
The invention includes a program code conversion processing method, as shown in fig. 1, comprising the steps of:
establishing a conversion relation between the entity class object and the data transmission object;
designating a conversion direction;
acquiring a receiving object corresponding to the conversion direction;
identifying the receiving object to obtain a calling code of the receiving object;
converting the call codes of the received objects into call codes of the target objects according to the conversion directions and the conversion relations;
when the receiving object is an entity class object, the target object is a data transmission object;
when the receiving object is a data transmission object, the target object is an entity class object.
In the above embodiment, the conversion relationship between the entity class object and the data transmission object is created, that is, the logical binding between the entity class object and the data transmission object is realized at one time, so that the subsequent conversion between the entity class object and the data transmission object is realized directly through the conversion relationship.
In the above embodiment, the receiving object to be converted is obtained by specifying the conversion direction.
In the above embodiment, the conversion of the entity class object and the data transmission object in the specified conversion direction is achieved by setting the conversion direction and creating the conversion relationship.
As a preferred embodiment, the data transfer object may be a DTO (Data Transfer Object) object.
As a preferred embodiment, the conversion relationship may be a conversion logic, where the conversion logic relies on Meta class automatically generated by apt, and a corresponding get method pointer is associated in Meta class, and the get method pointer is used for the method call provided by this embodiment, instead of reflection, so as to improve the performance during operation.
Further, as a preferred embodiment, establishing a conversion relationship between the entity class object and the data transmission object may include: and establishing a conversion relation between the entity class object and the calling codes corresponding to the homonymous fields in the data transmission object.
For example, the same name field may be the same name field of the same type, the entity class object includes a call code with a field of "age", and the data transmission object includes a call code with a field of "age", that is, the entity class object and the data transmission object both have a call code with the same name field of "age" (the storage type corresponding to the same name field of "age" herein is a long integer), so that a conversion relationship may be established between the call codes corresponding to the same name field in the entity class object and the data transmission object directly;
for example, the same name field may be a different type of same name field, taking the calling code with the field as "orders" included in the entity class object, and the calling code with the field as "orders" included in the data transmission object as an example, where the storage type corresponding to the field as "orders" in the entity class object is in the List manner of several orders, and only the number of orders is needed in the interface, so that the storage type corresponding to the field as "orders" in the data transmission object is in the decimal type, a conversion relationship may be established between the calling codes corresponding to the same name fields in both the entity class object and the data transmission object directly, and specifically, the calling code with the field as "orders" included in the entity class object is converted into the calling code corresponding to the orders. Size) stored in the data transmission object.
Further, as a preferred embodiment, establishing a conversion relationship between the entity class object and the data transmission object may include: establishing a conversion relation between the entity class object and the call codes corresponding to the same field data in the data transmission object;
for example, taking an example that the entity class object includes a calling code with a field of "orders", and the data transmission object includes a calling code with a field of "orderCount", the calling code with a field of "orders" in the entity class object represents List of a plurality of orders and is stored in the data transmission object, only the number of the calling codes is needed, only the following conversion relation is needed to be established, the calling code with a field of "orders" in the entity class object is converted into "orders.size ()", and the converted calling code of "orderCount" is stored in the data transmission object, as shown in the following specific code:
for example, taking an example that the entity class object includes call codes with fields of "orders" and "amounts", and the data transmission object includes call codes with fields of "orderamounts", the call codes with fields of "orders" in the entity class object are stored in a manner that the call codes with fields of "amounts" in the entity class object represent lists of a plurality of orders, and only the total of all order amounts is needed in the data transmission object, only the following conversion relation needs to be established, the call codes with fields of "orders" in the entity class object and the call codes with fields of "amounts" are accumulated, and then the call codes with fields of "orderamounts" in the data transmission object are stored, which are specifically as follows:
further, as a preferred embodiment, establishing a conversion relationship between the entity class object and the data transmission object may include: and establishing a conversion relation between the entity class object and the call codes corresponding to the similar remarks in the data transmission object.
Further, in the above embodiment, after establishing the conversion relationship between the entity class object and the data transmission object, the method further includes:
triggering alarm information when the calling code of the entity class object is changed; or (b)
When the calling code of the data transmission object changes, the alarm information is triggered.
For example, when a field corresponding to an entity class object is changed, a compiling error condition of "no existing" may occur in a calling code corresponding to the field, and at this time, alarm information may be sent to a developer, so as to guide the developer to quickly identify and correct.
As a preferred embodiment, the data fields required or not required can be declared by chained calls, the corresponding method is generated from APT, the input can be quickly searched by means of the method name prompt of IDE, if the input errors or the fields in the data transmission object and the entity class object are changed, the compiling can be failed, and thus the errors can be quickly found.
Further, as a preferred embodiment, establishing a conversion relationship between the entity class object and the data transmission object may include: establishing a conversion relation between the entity class object and a call code with an association relation in the data transmission object;
in the above preferred embodiment, a binding relationship between different fields may be specified, where there is an association relationship between different fields specified with a binding relationship, that is, there is an association relationship between call codes corresponding to fields, for example, taking a call code with a field of "orders" in an entity class object and a call code with a field of "orderCount" in a data transmission object as an example, the following binding relationship may be directly specified between the call code with a field of "orders" and the call code with a field of "orderCount"). Converting the calling code with the field of 'orders' in the entity class object into the calling code with the field of 'orderCount' in the data transmission object, so that the calling code with the association relationship between the entity class object and the data transmission object establishes a conversion relationship according to the binding relationship, thereby realizing the uniform conversion relationship.
Further, as a preferred embodiment, the conversion relation between the entity class object and the data transmission object is created through a syntax tree structure of the APT (Annotation Processing Tool, compile-time annotation processor).
In the above embodiment, the conversion relationship between the entity class object and the data transmission object is created through the syntax tree structure of the APT, so that the mutual conversion between the subsequent entity class object and the data transmission object is realized by means of the class library with high reusability of the APT.
Further, in the above embodiment, when the received object includes the call code corresponding to the privacy data;
and performing desensitization processing on the privacy data, so that after the conversion relation between the entity class object and the data transmission object is established, the condition that the privacy data in the received object is revealed through the call code of the target object obtained after conversion is avoided, and further, the conditions of back-end processing load, serialization load and network load are avoided.
Further, in the above embodiment, the converting direction includes:
converting the entity class object into a data transmission object; and
converting the data transmission object into an entity class object;
one of them.
In the above embodiment, the conversion direction is set, so that the conversion between the entity class object and the data transmission object according to the conversion direction is realized, and the privacy data in the entity class object is prevented from being unintentionally revealed in the conversion process.
As a preferred embodiment, when the conversion direction is to convert the entity class object into the data transmission object;
the receiving object obtained at the moment is an entity class object, namely the target object at the moment is a data transmission object;
identifying the entity class object to obtain a calling code of the entity class object;
and converting the calling codes in the entity class object into the calling codes of the data transmission object according to the conversion direction and the conversion relation and combining the conversion relation.
As a preferred embodiment, the above conversion processing method may be used to implement the conversion of the user record in the entity class object, where the conversion direction used at this time is that the entity class object is converted to the data transmission object, where the password and the mobile phone number in the user record are private data, so that the private data is desensitized during the conversion, and the order quantity and the order amount are returned, as shown in the following code:
public UserDto getUser(final Long id){
querying user records in a database
final User user＝userRepository.findById(id).orElseThrow(RuntimeException::new)；
Motor/forward converter User- > UserDto
return userConverterProvider.forward()
The// ignore password and handset number are not returned to the front end
.rejectRs(rs->rs.password().cellphone())
The amount of/additional return orders and the amount of orders, the conversion logic comes from the converter statement
.orderCount().orderAmount()
.convert(user)；
}
As a preferred embodiment, the above conversion processing method may be used to implement the conversion of the user list in the entity class object, where the conversion direction used at this time is that the entity class object is converted to the data transmission object, where the name, sex, and number of orders in the user list are returned after conversion, and other fields in the user list are used as the privacy data, so that the privacy data is subjected to desensitization processing during conversion, as shown in the following code:
public List<UserDto>listUsers(final UserSearchingRequest request){
obtaining user list according to search condition
final List<User>users＝userRepository.findAll(request)；
Motor/forward converter User- > UserDto
return userConverterProvider.forward()
Per default disable all field translations
.rejectAllRs()
The name, sex and order number are returned to the front end
.name().gender().orderCount()
.convert(users)；
}
As a preferred embodiment, when converting a data transfer object into an entity class object;
the receiving object obtained at the moment is a data transmission object, namely the target object at the moment is an entity class object;
identifying the data transmission object to obtain a calling code of the data transmission object;
and converting the calling codes in the data transmission object into the calling codes of the entity class object according to the conversion direction and the conversion relation and combining the conversion relation.
As a preferred embodiment, when the conversion direction is set to convert the data transmission object to the entity class object, a conversion relationship is set, and the conversion relationship may be "reject conversion id", "reject conversion creation time", "server current time as user creation time", and "save user information", as shown in the following code:
@Transactional
public void createUser(final UserDto userDto){
the/reverse converter UserDto-User
final User user＝userConverterProvider.backward()
The// reject transition id (id is automatically generated by the database, disregarded if the front-end is maliciously specified)
Creation time datetime of refusal conversion (datetime is generated by server, avoiding malicious request)
.rejectRs(rs->rs.id().datetime())
.convert(userDto)；
The current time of the/(server) is used as the user creation time
user.setDatetime(LocalDateTime.now())；
User information is/is saved
userRepository.save(user)；
}
As a preferred embodiment, when the conversion direction is set to convert the data transmission object into the entity class object, the conversion relationship is set, and the above conversion processing method may be used to query the user information in the database according to the data transmission object id, where the conversion relationship may be "reject conversion password", "reject conversion creation time", "merge userDto information into the user according to the binding relationship" and "save user information", as shown in the following code:
public void updateUser(final UserDto userDto){
querying user information in a database based on id in userDto
final User user＝userRepository.findById(userDto.getId()).orElseThrow(RuntimeException::new)；
The/reverse converter UserDto-User
userConverterProvider.backward()
The password is refused to be converted (the password modification should be processed by a special interface, the security operation such as the old password is required to be verified, the password information transmitted by the front end is disregarded when the user is modified)
Time datetime for creation of/rejection of conversion (datetime has been generated and cannot be modified by interface)
.rejectRs(rs->rs.password().datetime())
Merging userDto information into a user according to binding relationship
.merge(userDto,user)；
User information is/is saved
userRepository.save(user)；
}
Also included is a conversion processing system of program codes, including:
the relation determining module comprises a conversion relation between the entity class object and the data transmission object;
the direction determining module is used for designating a conversion direction;
the receiving module is used for acquiring a receiving object corresponding to the conversion direction;
the recognition module is used for converting the calling codes of the received objects into the calling codes of the target objects according to the conversion direction and the conversion relation;
the conversion module is used for converting the calling code of the receiving object into the calling code of the target object by adopting the converter according to the conversion direction;
when the receiving object is an entity class object, the target object is a data transmission object;
when the receiving object is a data transmission object, the target object is an entity class object.
The specific implementation manner of the program code conversion processing system of the present invention is basically the same as the above embodiments of the program code conversion processing method, and will not be described herein.
The computer-readable storage medium is provided with a calling program which can be executed on a processor, and the calling program is executed by the processor to implement the method for converting the program code of any one of the above.
The specific embodiments of the computer readable storage medium of the present invention are basically the same as the embodiments of the conversion processing method of the program code, and are not described herein.
The foregoing is merely illustrative of the preferred embodiments of the present invention and is not intended to limit the embodiments and scope of the present invention, and it should be appreciated by those skilled in the art that equivalent substitutions and obvious variations may be made using the description and illustrations of the present invention, and are intended to be included in the scope of the present invention.
Claims (5)
1. A program code conversion processing method, characterized by comprising the steps of:
establishing a conversion relation between the entity class object and the data transmission object, including: establishing a conversion relation between the entity class object and the calling codes corresponding to the homonymous fields in the data transmission object; establishing a conversion relation between the entity class object and the calling codes corresponding to the same field data in the data transmission object; establishing a conversion relation between the entity class object and a call code corresponding to a similar remark in the data transmission object; establishing a conversion relation between the entity class object and a call code with an association relation in the data transmission object;
establishing a conversion relation between an entity class object and a data transmission object through an APT grammar tree structure, wherein the conversion relation is a Meta class which is automatically generated by depending on the APT, and the Meta class is associated with a corresponding get method pointer and a corresponding set method pointer;
designating a conversion direction; acquiring a receiving object corresponding to the conversion direction;
identifying the receiving object to obtain a calling code of the receiving object;
converting the call codes of the received objects into call codes of target objects according to the conversion directions and the conversion relations;
when the receiving object is the entity class object, the target object is the data transmission object; when the receiving object is the data transmission object, the target object is the entity class object;
when the conversion direction is that the entity class object is converted into the data transmission object, and when the receiving object comprises the calling code corresponding to the privacy data, the privacy data is subjected to desensitization processing, so that after the conversion relation between the entity class object and the data transmission object is established, the privacy data in the receiving object is prevented from being revealed through the calling code of the target object obtained after the conversion.
2. The conversion processing method of program code according to claim 1, wherein the conversion direction includes:
converting the entity class object into the data transmission object; and
converting the data transmission object into the entity class object;
one of them.
3. The conversion processing method of program code according to claim 1, wherein the data transmission object is a DTO object.
4. A conversion processing system of program codes, comprising:
the relation determining module comprises a conversion relation between the entity class object and the data transmission object,
the direction determining module is used for designating a conversion direction;
the receiving module is used for acquiring a receiving object corresponding to the conversion direction;
the identification module is used for identifying the receiving object to acquire a calling code of the receiving object;
the conversion module is used for converting the calling codes of the receiving objects into the calling codes of the target objects according to the conversion directions and in combination with the conversion relations;
when the receiving object is the entity class object, the target object is the data transmission object;
when the receiving object is the data transmission object, the target object is the entity class object;
the establishing of the conversion relation comprises the following steps: establishing a conversion relation between the entity class object and the calling codes corresponding to the homonymous fields in the data transmission object; establishing a conversion relation between the entity class object and the calling codes corresponding to the same field data in the data transmission object; establishing a conversion relation between the entity class object and a call code corresponding to a similar remark in the data transmission object; establishing a conversion relation between the entity class object and a call code with an association relation in the data transmission object;
establishing a conversion relation between an entity class object and a data transmission object through an APT grammar tree structure, wherein the conversion relation is a Meta class which is automatically generated by depending on the APT, and the Meta class is associated with a corresponding get method pointer and a corresponding set method pointer;
when the conversion direction is that the entity class object is converted into the data transmission object, and when the receiving object comprises the calling code corresponding to the privacy data, the privacy data is subjected to desensitization processing, so that after the conversion relation between the entity class object and the data transmission object is established, the privacy data in the receiving object is prevented from being revealed through the calling code of the target object obtained after the conversion.
5. A computer-readable storage medium, wherein a calling program executable on a processor is stored on the computer-readable storage medium, and the calling program when executed by the processor implements the program code conversion processing method according to any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110476837.3A CN113110847B (en) | 2021-04-29 | 2021-04-29 | Conversion processing method and system for program codes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110476837.3A CN113110847B (en) | 2021-04-29 | 2021-04-29 | Conversion processing method and system for program codes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113110847A CN113110847A (en) | 2021-07-13 |
| CN113110847B true CN113110847B (en) | 2024-02-13 |
Family
ID=76720651
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110476837.3A Active CN113110847B (en) | 2021-04-29 | 2021-04-29 | Conversion processing method and system for program codes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113110847B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104731911A (en) * | 2015-03-24 | 2015-06-24 | 浪潮集团有限公司 | Dynamic mapping and conversion method of data table and entity class |
| CN109582481A (en) * | 2019-01-10 | 2019-04-05 | 北京城市网邻信息技术有限公司 | Transmission method, device, equipment and the storage medium of call result |
| CN109710218A (en) * | 2018-11-26 | 2019-05-03 | 福建天泉教育科技有限公司 | A kind of object automatic switching method and terminal |
| CN109901822A (en) * | 2019-01-08 | 2019-06-18 | 平安科技（深圳）有限公司 | The mutual shifting method of object, device and storage medium, server |
| CN112667240A (en) * | 2020-12-23 | 2021-04-16 | 平安普惠企业管理有限公司 | Program code conversion method and related device |
-
2021
- 2021-04-29 CN CN202110476837.3A patent/CN113110847B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104731911A (en) * | 2015-03-24 | 2015-06-24 | 浪潮集团有限公司 | Dynamic mapping and conversion method of data table and entity class |
| CN109710218A (en) * | 2018-11-26 | 2019-05-03 | 福建天泉教育科技有限公司 | A kind of object automatic switching method and terminal |
| CN109901822A (en) * | 2019-01-08 | 2019-06-18 | 平安科技（深圳）有限公司 | The mutual shifting method of object, device and storage medium, server |
| CN109582481A (en) * | 2019-01-10 | 2019-04-05 | 北京城市网邻信息技术有限公司 | Transmission method, device, equipment and the storage medium of call result |
| CN112667240A (en) * | 2020-12-23 | 2021-04-16 | 平安普惠企业管理有限公司 | Program code conversion method and related device |
Non-Patent Citations (1)
| Title |
|---|
| java反射+注解实现Entity 类与Dto 类相互转换;Mr_Precious;《https://www.cnblogs.com/scale-lai/p/10164634.htm》;20181224;第1-6页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113110847A (en) | 2021-07-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101150065B1 (en) | Ability for developers to easily find or extend well known locations on a system | |
| RU2377634C2 (en) | Licensing program interface | |
| US11327727B2 (en) | Systems and methods for integrating modules into a software application | |
| CN110032568B (en) | Data structure reading and updating method and device, and electronic equipment | |
| CN113076153A (en) | Interface calling method and device | |
| CN114722036A (en) | Data processing method and device, electronic equipment and readable storage medium | |
| CN113110847B (en) | Conversion processing method and system for program codes | |
| CN108959294B (en) | Method and device for accessing search engine | |
| US7441252B2 (en) | Cache control device, and method and computer program for the same | |
| CN115269040B (en) | Tenant business application expanding method, device and system | |
| CN113468446B (en) | Method, system and equipment for supporting identification of third party two-dimensional code data | |
| CN114936368A (en) | Java memory Trojan detection method, terminal device and storage medium | |
| CN113282906B (en) | Authority detection method, device, terminal and storage medium | |
| CN111045983B (en) | Nuclear power station electronic file management method, device, terminal equipment and medium | |
| CN112148710B (en) | Micro-service library separation method, system and medium | |
| CN109918895B (en) | Method, electronic device, and computer-readable medium for outputting data | |
| CN116301758B (en) | Rule editing method, device, equipment and medium based on event time points | |
| CN116974653B (en) | Class loading method and system | |
| CN111142856B (en) | Automatic picture identification database resource table establishment method and system | |
| CN111045657B (en) | Program code operation method and device, and compiling method and device | |
| KR20070106327A (en) | Method of user definition data searching and system thereof | |
| CN115168459A (en) | Data acquisition method and device | |
| CN117014515A (en) | Business processing method, device, equipment and storage medium based on micro-service | |
| CN113672309A (en) | Business service method, device, electronic equipment and readable storage medium | |
| CN117217173A (en) | Document processing method, device, server and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |