WO2019028989A1 - 一种代码分析方法及终端设备 - Google Patents
一种代码分析方法及终端设备 Download PDFInfo
- Publication number
- WO2019028989A1 WO2019028989A1 PCT/CN2017/104535 CN2017104535W WO2019028989A1 WO 2019028989 A1 WO2019028989 A1 WO 2019028989A1 CN 2017104535 W CN2017104535 W CN 2017104535W WO 2019028989 A1 WO2019028989 A1 WO 2019028989A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- call
- path
- relationship
- file
- found
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
- G06F11/3612—Software analysis for verifying properties of programs by runtime analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Definitions
- This application belongs to the field of computer technology, and in particular, to a code analysis method and a terminal device.
- the embodiment of the present application provides a code analysis method and a terminal device, so as to solve the problem that the existing caller manually combs the call relationship, and the efficiency is low and the error rate is high.
- a first aspect of the embodiments of the present application provides a code analysis method, which may include:
- a second aspect of the embodiments of the present application provides a computer readable storage medium storing computer readable instructions, the computer readable instructions being executed by a processor, and implementing the following steps:
- a third aspect of the embodiments of the present application provides a code analysis terminal device, including a memory, a processor, and computer readable instructions stored in the memory and operable on the processor, the processing The computer executes the computer readable instructions to implement the following steps:
- a fourth aspect of the embodiments of the present application provides a computer readable instruction, the computer readable instructions being applied to a code analysis terminal device, where the code analysis terminal device includes a memory, a processor, and a storage device
- the computer readable instructions in a memory and operative on the processor, the computer readable instructions comprising the following modules:
- a path obtaining module configured to acquire an absolute path of a source file of the target Java project
- a search module configured to find a first method corresponding to the specified URL from the class file in the absolute path;
- calling a lookup module configured to search for a call to the second method in the method body of the first method, where the second method is a method different from the first method;
- a second method configured to: if the calling of the second method is found in the method body of the first method, searching for the second method in a class file;
- a call relationship record module configured to record a call relationship between the first method and the second method if the second method is found in a class file
- a first method update module configured to determine the second method as a new first method, and return to perform the step of searching for a call to the second method in the method body of the first method;
- a call relationship summary module configured to: if the call to the second method is not found in the method body of the first method, end code analysis, and summarize the recorded call relationship;
- calling a relationship drawing module configured to draw a corresponding effect of the corresponding call relationship diagram according to the summarized calling relationship Beneficial effect
- the beneficial effects of the embodiment of the present application compared with the prior art are as follows: The embodiment of the present application first obtains an absolute path of a source file of a target Java project, and searches for a class file from the absolute path. The first method corresponding to the specified URL, and then through recursion, find the call to the next level method layer by layer until there is no next level method, and finally summarize all the call relationships of the record and draw corresponding Call graph. The issuer only needs to specify the URL that needs to be analyzed, and then automatically analyzes the call relationship and draws the call relationship graph, which greatly improves the analysis efficiency, and avoids the occurrence of human error, effectively reducing the error rate.
- FIG. 1 is a flow chart of an embodiment of a code analysis method in an embodiment of the present application.
- FIG. 2 is a schematic diagram of generating a drawing script according to a script template according to a code analysis method in an embodiment of the present application
- FIG. 3 is a schematic diagram of an effect of a call relationship diagram generated by a code analysis method according to an embodiment of the present application
- FIG. 4 is a schematic block diagram of a code analysis terminal device according to an embodiment of the present application
- FIG. 5 is a functional block diagram of a code analysis program according to an embodiment of the present application.
- the embodiment of the present invention mainly analyzes the Java code and generates a call relationship diagram.
- a lot of technical terms related to Java code are involved. For the sake of understanding, these technical terms are first explained briefly.
- Absolute path The path to the complete description file location is the absolute path, that is, the path from the root directory at the top of the tree directory structure to a directory or file, consisting of a series of consecutive directories, with a diagonal Line separated, until the directory or file to be specified, the last name in the path is the directory or file to point to, such as C: ⁇ windows ⁇ system32 ⁇ cmcLexe.
- the relative path is the path starting from the current path. For example, the current path is C: ⁇ windows. Using the relative path, the path should be . ⁇ system32 ⁇ cmd.exe.
- URL Uniform Resource Locator, which is a uniform resource locator.
- a URL is a compact representation of the location and access method of a resource that can be obtained from the Internet, and is the address of a standard resource on the Internet.
- Method In Java code, a method is a set of code blocks for implementing a specific function, which acts like a function in C code.
- Class In Java code, a class is a collection of objects with the same characteristics and behavior, in a nutshell
- the class is the template for creating Java objects.
- An object is an instance of a class that has state and behavior.
- a dog is an object whose status is: color, name, breed; behaviors are: wagtail, call, eat, etc.
- Database operation class The class provided by the system to operate on the database can access various types of databases, establish database connections, execute SQL statements, and access data.
- PlantUML PlantUML is a rapid creation of Unified Modeling (Unified Modeling)
- UML A component of graphics, where UML is a general-purpose, unified graphical model language for object-oriented software bursting. It is an effective tool for software system stats, visualization, and modeling.
- An embodiment of a code analysis method in the embodiment of the present application may include:
- Step S101 Obtain an absolute path of the source file of the target Java project.
- Classpath In Java, the role of Classpath is to tell the Java execution environment, in which directories you can find the classes or packages needed for the Java program to be executed. Here you can enter the Java execution environment and the operating system. Row analogy, if the path variable is set to let the operating system find the specified utility program (in Windows, it is to find the .exe file), then the purpose of setting the Classpath is to let the Java execution environment find the specified Java program (that is, the .class file). ).
- the source path and the compiled path are parsed from the environment variable.
- a source code path such as a Java code path, a Class file path, and a Jar package file path is provided, and a compilation path of the Java code is provided, where the path information needs to be parsed therefrom.
- an absolute path of the source file of the target Java project is determined according to the source code path and the compilation path.
- the class file in the absolute path is loaded into the virtual machine memory through the Classloader, so as to be used for subsequent lookup.
- the Classloader is a class loader for loading Java classes into the Java virtual machine. Unlike ordinary programs, Java class files are not native executables. When running a Java program, run the Java virtual machine first, then load the class file into the virtual machine.
- Step S102 Find a first method corresponding to the specified URL from the class file in the absolute path.
- the user may input one or more URLs in advance.
- multiple URLs may be processed simultaneously to generate corresponding multiple call relationship diagrams.
- the following descriptions are performed by using one URL.
- the case of the URL can be pushed by analogy.
- the corresponding method may be found in the class file pabrBaseSetController.java in the absolute path, that is, the first method: pabrBaseSetController°
- Step S103 searching for a call to the second method in the method body of the first method.
- the second method is a method different from the first method.
- the second method is a method for injecting attributes by spring marked by @Au towired. If the calling of the second method is found in the method body of the first method, step S104 to step S106 are performed, if the second method is not found in the method body of the first method If the call is made, step S107 is performed.
- Step S104 searching for the second method in a class file.
- Step S105 Record a calling relationship between the first method and the second method.
- Step S106 determining the second method as a new first method.
- step S103 After determining the new first method, it is necessary to return to step S103, that is, to find the call of the second method in the method body of the new first method. It is easy to understand that this is a recursive process that finds the calls to the next level of methods one level at a time.
- a call to the new method is found in the method body of the first method pabrBaseSetController. If a call to the second method pabrBaseSetWsa is found in the method body of the first method pabrBaseSetController, the class file corresponding thereto is first determined. The file path, and then get the class file pabrBaseSetWsa.java under the path, and finally find the second method pabrBaseSetWsa in the class file, recording the first method pabrBaseSetController called the second method pabrBaseSetWsa.
- the call to the new method is found. If the call to the third method pabrBaseSetService can be found in the method body of the second method pabrBaseSetWsa, the method of the third method is first determined. Name the file path of the corresponding class file, and then obtain the class file pabrBaseSetService.java under the path, and finally find the third method pa brBaseSetService in the class file, record the second method pabrBaseSetWsa calls the third method pabrBaseSetSe rvice°
- the method may further include:
- the class to which the current method belongs is a subclass of the database operation class provided by the framework, the call to the parameter of the string type is found in the method body of the current method;
- the string is The parameter of the type is determined to be the database identifier corresponding to the current method.
- the class to which the current method pabrBaseSetDao belongs is a subclass of the database operation class provided by the framework
- the method body of the current method pabrBaseSetDao Find the call to the parameter of the string type. If the call to the parameter "GETPABRCRITICALISSUELIST" of the string type is found in its method body, the database identifier corresponding to the current method pabrBaseSetDao can be determined, that is, SQL.
- the ID is "GETPABRCRITICALISSUELIST,,.
- Step S107 ending the code analysis, and summarizing the recorded call relationship.
- Method pabrBaseSetController calls the method pabrBaseSetWsa
- the method pabrBaseSetWsa calls the method pabrBaseSetService
- Method pabrBaseSetService calls the method pabrBaseSetDao
- pabrBaseSetController is a network layer method
- pabrBaseSetWsa and pabrBaseSetSer vice are application layer methods
- pabrBaseSetDao is a corresponding database layer method
- Step S108 Draw a corresponding call relationship graph according to the summarized call relationship.
- PlantUML for graphic drawing, it is generally scripted manually, and for each graphic, the corresponding PlantUML script is written, which is obviously laborious and laborious, and Error-prone.
- a new scripting method is adopted, that is, a general PlantUML script template for drawing a call relationship diagram is set in advance, and the script template is formally related to a normal drawing call relationship diagram.
- the PlantUML script is no different, but it leaves up the location of the script that fills in each specific call relationship. Record and mark the locations of these scripts that fill the call relationship, for example, record them as: script location 1, script location 2, script location 3, script location 4, etc.
- the number of these script locations can be According to the actual situation, it is guaranteed that it can accommodate the complete calling relationship in the code. For example, if you know that the calling relationship of a Java code is within 10 layers, you can set the number of script positions to 10
- the call relationships summarized in step S107 are also numbered, for example, the call relationship 1 is p abrBaseSetController--l>pabrBaseSetWsa (ie, the method pabrBaseSetController calls the method pabrBaseSetWsa), and the call relationship 2 is pabrBaseSetWsa-pabrBaseSetService ( That is, the method p abrBaseSetWsa calls the method pabrBaseSetService) , the calling relationship 3 is pabrBaseSetService --bpabrBaseSetDao (that is, the method pabrBaseSetService calls the method pabrBaseSetDao), and the calling relationship 4 is pabrBaseSetDao — l>SQL
- GETPABRCRITICALISSUELIST ie the SQL ID corresponding to the method pabrBaseSetDao is "GETPABRCRITICALISSUELIST"
- these call relationships are respectively filled in the corresponding script positions, and the script pabrBaseSetController-pabrBaseSetWsa calling the relationship 1 is filled in the script position 1, and the script pabrBaseSetWsa pabrBaseSetService calling the relationship 2 is filled in.
- the script position 2 and so on, until all the call relationship scripts are filled into the corresponding script position, the script position remaining in the script template is removed, and the drawing script of the call relationship graph is obtained, and the operation script is executed.
- the call graph can be generated by generating a script.
- FIG. 3 is a call relationship diagram generated according to a preset script template
- a call relationship diagram of different presentation modes can be generated by using different script templates
- FIG. 3 Only one of the effects is indicated.
- the user can select an appropriate script template according to the actual situation, which is not specifically limited in this embodiment.
- the embodiment of the present application first obtains an absolute path of a source file of a target Java project, and searches for a first method corresponding to the specified URL from the class file in the absolute path, and then passes Recursive Find the call to the next level method layer by layer until there is no next level method, and finally summarize all the call relationships recorded and draw the corresponding call relationship graph.
- the issuer only needs to specify the URL to be analyzed, and then automatically completes the analysis of the call relationship and draws the call relationship diagram, which greatly improves the analysis efficiency, and avoids the occurrence of human error, effectively reducing the error rate.
- FIG. 4 is a schematic block diagram of the code analysis terminal device provided by the embodiment of the present application. For the convenience of description, only the related to the embodiment of the present application is shown. section.
- the code analysis terminal device may be a computing device such as a desktop computer, a notebook, a palmtop computer, or a cloud server.
- the code analysis terminal device can include: a processor 40, a memory 41, and computer readable instructions 42 stored in the memory 41 and executable on the processor 40.
- the processor 40 may be a central processing unit (CPU), or may be another general-purpose processor, a digital signal processor (DSP), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array
- CPU central processing unit
- DSP digital signal processor
- ASIC Application Specific Integrated Circuit
- the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
- the memory 41 may be an internal storage unit of the code analysis terminal device 4, such as a hard disk or a memory of the code analysis terminal device 4.
- the memory 41 may also be an external storage device of the code analysis terminal device 4, such as a plug-in hard disk equipped with the code analysis terminal device 4, a smart memory card (SMC), and a secure digital (Secure) Digital, SD) cards, flash cards, etc.
- the memory 41 may also include both an internal storage unit of the code analysis terminal device 4 and an external storage device.
- the memory 41 is for storing the computer readable instructions and other programs and data required by the code analysis terminal device 4.
- the memory 41 can also be used to temporarily store data that has been output or is about to be output.
- FIG. 5 is a functional block diagram of computer readable instructions 42 provided by an embodiment of the present application.
- the computer readable instructions 42 may be partitioned into one or more modules, the one or more modules being stored in the memory 41 and executed by the processor 40 to complete This application.
- the computer readable instructions 42 may be divided into a path acquisition module 501, a first method lookup module 502, a call lookup module 503, a second method lookup module 504, a call relationship record module 505, A method update module 506, a call relationship summary module 507, and a call relationship graph drawing module 508.
- a module as referred to in this application refers to a series of computer readable instruction instructions that are capable of performing a particular function, and are more suitable than the program to describe the execution of the computer readable instructions 42 in the code analysis terminal. The following description will specifically describe the functions of the modules 501-508.
- the path obtaining module 501 is configured to obtain an absolute path of the source file of the target Java project.
- the first method searching module 502 is configured to find a first method corresponding to the specified UR L from the class file in the absolute path.
- the calling search module 503 is configured to search for a call to the second method in the method body of the first method, where the second method is a method different from the first method;
- the second method searching module 504 is configured to: if the calling of the second method is found in the method body of the first method, searching for the second method in a class file;
- the call relationship record module 505 is configured to: if the second method is found in the class file, record a call relationship between the first method and the second method;
- the first method update module 506 is configured to determine the second method as a new first method, and return to perform the step of searching for a call to the second method in the method body of the first method. ;
- the call relationship summary module 507 is configured to: if the call to the second method is not found in the method body of the first method, end code analysis, and summarize the recorded call relationship;
- the call graph drawing module 508 is configured to draw a corresponding call relationship graph according to the summarized call relationship.
- the path obtaining module 501 may include:
- an environment variable obtaining unit configured to acquire an environment variable of the target Java project
- a parsing unit configured to parse the source path and the compile path from the environment variable
- an absolute path determining unit configured to determine an absolute path of the source file of the target Ja va project according to the source path and the compiled path.
- the second method searching module 504 may include:
- a file path determining unit configured to determine a file path of the class file corresponding to the method name of the second method
- a class file obtaining unit configured to acquire a class file in the file path
- the second method searching unit is configured to search the second method in the class file.
- the call graph drawing module 508 may include:
- a drawing script generating unit configured to import the summarized calling relationship into a preset PlantUML script template, and generate a drawing script of the calling relationship graph;
- a call relationship generating unit configured to run the drawing script, and generate the calling relationship diagram corresponding to the summarized calling relationship.
- the computer readable instructions 42 may further include:
- the parameter calling the search module is configured to: if the class to which the first method belongs is a subclass of the database operation class provided by the framework, look for a call to the parameter of the string type in the method body of the first method. ;
- a database identifier determining module configured to: if a call to a parameter of a string type is found in a method body of the first method, determine a parameter of the string type to correspond to the first method Database ID.
- modules, units, and/or method steps of various embodiments described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. achieve. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
- the disclosed system, apparatus, and method may be implemented in other manners.
- the device embodiments described above are merely illustrative,
- the division of the unit is only a logical function division, and the actual implementation may have another division manner, for example, multiple units or components may be combined or may be integrated into another system, or some features may be ignored, or not. carried out.
- the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
- the unit described as a separate component may or may not be physically distributed, and the component displayed as a unit may or may not be a physical unit, that is, may be located in one place, or may be distributed to multiple On the network unit. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
- each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
- the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
- the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
- a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
- the foregoing storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710675458.0A CN107506299B (zh) | 2017-08-09 | 2017-08-09 | 一种代码分析方法及终端设备 |
CN201710675458.0 | 2017-08-09 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019028989A1 true WO2019028989A1 (zh) | 2019-02-14 |
Family
ID=60690618
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/104535 WO2019028989A1 (zh) | 2017-08-09 | 2017-09-29 | 一种代码分析方法及终端设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN107506299B (zh) |
WO (1) | WO2019028989A1 (zh) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111008022B (zh) * | 2019-12-04 | 2023-12-12 | 浙江大搜车软件技术有限公司 | 关系图生成方法、装置、计算机设备和存储介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5802367A (en) * | 1995-07-07 | 1998-09-01 | Microsoft Corporation | Method and system for transparently executing code using a surrogate process |
CN101482847A (zh) * | 2009-01-19 | 2009-07-15 | 北京邮电大学 | 一种基于安全漏洞缺陷模式的检测方法 |
CN103678097A (zh) * | 2012-09-05 | 2014-03-26 | 百度在线网络技术(北京)有限公司 | 一种选择回归测试用例的方法和装置 |
CN106020848A (zh) * | 2016-06-07 | 2016-10-12 | 北京信息科技大学 | 面向c#的函数调用路径生成方法 |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100576172C (zh) * | 2008-05-27 | 2009-12-30 | 华耀环宇科技(北京)有限公司 | 一种通过分析代码变化确定功能点变化的方法 |
CA2687672A1 (en) * | 2009-12-07 | 2011-06-07 | Ibm Canada Limited - Ibm Canada Limitee | Intelligent call graph generation |
US8954929B2 (en) * | 2010-03-29 | 2015-02-10 | Microsoft Corporation | Automatically redirecting method calls for unit testing |
US20110321013A1 (en) * | 2010-06-23 | 2011-12-29 | Quickunit Ltd | Interactive environment for test case generation associated with a computer code |
CN102012833A (zh) * | 2010-11-09 | 2011-04-13 | 北京神舟航天软件技术有限公司 | 基于编译过程中间结果的静态堆栈检测方法 |
CN103186406B (zh) * | 2011-12-30 | 2016-08-17 | 国际商业机器公司 | 用于控制流分析的方法和装置 |
CN104536895B (zh) * | 2015-01-12 | 2017-06-09 | 牟永敏 | 一种面向Java函数调用路径的测试过程跟踪方法及系统 |
CN104899147B (zh) * | 2015-06-19 | 2017-11-28 | 北京理工大学 | 一种面向安全检查的代码静态分析方法 |
CN105095092A (zh) * | 2015-09-25 | 2015-11-25 | 南京大学 | 基于静态分析和动态运行的Web应用JavaScript代码原子性违反检测 |
CN105808252A (zh) * | 2016-03-04 | 2016-07-27 | 北京理工大学 | 一种Windows操作系统内核函数遍历方法 |
CN106528422B (zh) * | 2016-11-10 | 2019-01-29 | 中国银联股份有限公司 | 一种检测Java程序页面扰动的方法和装置 |
-
2017
- 2017-08-09 CN CN201710675458.0A patent/CN107506299B/zh active Active
- 2017-09-29 WO PCT/CN2017/104535 patent/WO2019028989A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5802367A (en) * | 1995-07-07 | 1998-09-01 | Microsoft Corporation | Method and system for transparently executing code using a surrogate process |
CN101482847A (zh) * | 2009-01-19 | 2009-07-15 | 北京邮电大学 | 一种基于安全漏洞缺陷模式的检测方法 |
CN103678097A (zh) * | 2012-09-05 | 2014-03-26 | 百度在线网络技术(北京)有限公司 | 一种选择回归测试用例的方法和装置 |
CN106020848A (zh) * | 2016-06-07 | 2016-10-12 | 北京信息科技大学 | 面向c#的函数调用路径生成方法 |
Also Published As
Publication number | Publication date |
---|---|
CN107506299A (zh) | 2017-12-22 |
CN107506299B (zh) | 2021-04-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10169471B2 (en) | Generating and executing query language statements from natural language | |
WO2019029155A1 (zh) | 数据对比方法、装置、计算机设备和存储介质 | |
CN108459962A (zh) | 代码规范性检测方法、装置、终端设备及存储介质 | |
WO2019169723A1 (zh) | 测试用例选择方法、装置、设备以及计算机可读存储介质 | |
CN111177113B (zh) | 数据迁移方法、装置、计算机设备和存储介质 | |
CN110825430A (zh) | 一种api文档生成方法、装置、设备及存储介质 | |
US11366704B2 (en) | Configurable analytics for microservices performance analysis | |
US10693962B1 (en) | Language and mechanism for modeling and exporting storage platform topologies, attributes, and behaviors | |
CN112187713B (zh) | 报文转换的方法、装置、计算机设备和存储介质 | |
CN114138748A (zh) | 数据库映射文件生成方法、装置、设备及存储介质 | |
US11645234B2 (en) | Rule-based collections of subset(s) of metadata in response to a trigger event occurring | |
CN112286557B (zh) | 一种非覆盖式更新代码内容的方法和装置 | |
CN111158665B (zh) | 代码生成方法及装置、电子设备和存储介质 | |
CN110633162B (zh) | 远程调用实现方法、装置、计算机设备及存储介质 | |
KR102132449B1 (ko) | 자바스크립트 파일 재작성을 통한 자바스크립트 해석 엔진 테스트 방법 및 장치 | |
WO2019028989A1 (zh) | 一种代码分析方法及终端设备 | |
CN114115900B (zh) | 一种脚本编译方法、装置及电子设备 | |
CN116400914A (zh) | 一种基于数据模型快速构建web应用的方法 | |
US9201937B2 (en) | Rapid provisioning of information for business analytics | |
CN113495723B (zh) | 一种调用功能组件的方法、装置及存储介质 | |
CN111159203B (zh) | 一种数据关联分析的方法、平台、电子设备及存储介质 | |
CN111124386B (zh) | 基于Unity的动画事件处理方法、装置、设备和存储介质 | |
WO2022105494A1 (zh) | 数据自动回填方法、装置、电子设备及计算机存储介质 | |
CN114218261A (zh) | 数据查询方法、装置、存储介质以及电子设备 | |
CN113761040A (zh) | 数据库与应用程序双向映射方法、设备、介质及程序产品 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17920725 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 17920725 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 03.08.2020) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 17920725 Country of ref document: EP Kind code of ref document: A1 |