CN104699547B - JavaEE applications class load conflict analysis method and device - Google Patents
JavaEE applications class load conflict analysis method and device Download PDFInfo
- Publication number
- CN104699547B CN104699547B CN201510121221.9A CN201510121221A CN104699547B CN 104699547 B CN104699547 B CN 104699547B CN 201510121221 A CN201510121221 A CN 201510121221A CN 104699547 B CN104699547 B CN 104699547B
- Authority
- CN
- China
- Prior art keywords
- class
- classloader
- application
- analyzed
- conflict
- 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
Landscapes
- Stored Programmes (AREA)
Abstract
The embodiment of the invention discloses a kind of JavaEE applications class load conflict analysis method and devices, it is related to computer application technology, solve existing JavaEE applications class load mechanism there are potential class load conflict risk and is difficult to position the defects of potentially conflicting class.A kind of JavaEE applications class load conflict analysis method of the present invention includes：Obtain the corresponding Classloader chain of application to be analyzed；Based on the Classloader chain, conflict analysis is carried out to all non-duplicate class files of the application to be analyzed, to determine potential conflict class.
Description
Technical field
The present invention relates to computer application technology more particularly to a kind of JavaEE applications class load conflict analysis methods
And device.
Background technology
The execution of java application often relies on multiple jar files and Java Virtual Machine（Java Virtual
Machine, abbreviation JVM）, wherein, jar file includes class file（Suffix is the file of .class）, and class file needs to add
Being downloaded in JVM could run.
The component for being responsible for loading class file in JVM is known as Classloader, and JVM contains a Classloader in itself, claims
To guide Classloader, guiding Classloader is realized with local code, it is responsible for loading the core classes of Java, such as Java_
home/jre/rt.jar（Java_home is the installation directory of JDK）In class, other than guiding Classloader, JVM is also carried
Two Classloaders have been supplied, have respectively extended Classloader and system Classloader, what they were realized with Java language,
In, extension Classloader is responsible for loading the extension class of Java, in jar file under Java_home/jre/lib/ext catalogues
Class, system Classloader are responsible for the class of loading application programs itself needs, the class such as specified by "-classpath " parameter with
The class that system environment variable " CLASSPATH " is specified.Other than guiding Classloader, each Classloader can set it
Parent loader, five-star parent loader are guiding Classloader, can thus form a Classloader chain.
The class stress model that JVM acquiescences use is the preferential stress model of father, and client model or parents is also made to appoint model,
Under this model, subclass loader entrusts parent loader to load first when a class is loaded, and so on, if
All parent loaders cannot be all loaded into, then subclass loader is loaded again.In addition, JVM also provide it is self-defined
Classloader, self defined class loader can not carry out, such as subclass when loading classes according to the preferential stress model of father
Loader can be loaded preferentially, if loading, less than being loaded again by parent loader, it is preferential that such class stress model is known as son
Stress model.JavaEE application servers had both supported the preferential stress model of father or had supported the preferential stress model of son.
In JVM, a Classloader can make caching process to the class loaded, first when a class is loaded
Search whether to have loaded in the buffer, no longer be loaded if having loaded, if not loading again into
Row loading, i.e., same class can be only loaded once；Meanwhile different each Self managements of Classloader had loaded the caching of class,
These cachings are sightless to other Classloaders.
In the research and practice process to the prior art, inventor has found that at least there are following technologies in the prior art to ask
Topic：
1）Since same class can be only loaded once, there are classes for different jar files in the class.path of JavaEE applications
In the case of the identical class of full name, it is impossible to guarantee to be loaded into expected class, may result in java applet operation error in this way,
For example, for multiple versions of a jar file in the class.path of a JavaEE application, program is loaded with incorrect version
It can lead to program operation error.
2）Since the caching of the loading classes of different Classloader management is invisible to other Classloaders, then just having can
The phenomenon that same class is by repeated loading can occur, for example, the Classloader of a JavaEE application is loaded using sub- priority class,
It is preferentially loaded from itself class.path in loading classes, if it is possible to which loading is then loaded, and parent loader just
Loaded it is such, this there have been same class by multiple Classloader repeated loadings the phenomenon that, and think not in JVM
Class with Classloader loading is different class, i.e. the type of these classes is incompatible, so that in behaviour such as type conversions
Lead to program operation error in work.
3）Whole classes in class.path will not be loaded immediately due to JVM, but loaded as needed when program is run
, cause program operation error that can't expose immediately by class loading in this way, so as to form the running potential risk of program.
It can be seen that existing JavaEE applications class load mechanism is there are potential class load conflict risk, and position
Potential conflict class is not easily, in the case of especially containing a large amount of jar file in JavaEE applications, to determine
Position potential conflict class can be more difficult.
Invention content
The present invention provides a kind of JavaEE applications class load conflict analysis method and device, can realize and JavaEE is applied
Comprehensive analysis of potential class load conflict risk in program operation, to determine potential conflict class in time.
On the one hand, the present invention provides a kind of JavaEE applications class load conflict analysis method, the method includes：
Obtain the corresponding Classloader chain of application to be analyzed；
Based on the Classloader chain, conflict analysis is carried out to all non-duplicate class files of the application to be analyzed, with
Determine potential conflict class.
On the other hand, the present invention provides a kind of JavaEE applications class load conflict analytical equipment, and described device adds including class
Device management module and class load conflict analysis module are carried, wherein,
The Classloader management module, for obtaining the corresponding Classloader chain of application to be analyzed；
The class load conflict analysis module for being based on the Classloader chain, owns the application to be analyzed
Non-duplicate class file carries out conflict analysis, to determine potential conflict class.
JavaEE applications class load conflict analysis method provided by the invention and device obtain the corresponding class of application to be analyzed
Loader chain；Based on the Classloader chain, conflict analysis is carried out to all non-duplicate class files of the application to be analyzed, with
Determine potential conflict class.Compared with prior art, the Classloader chain can be based on, is realized to JavaEE application programs
The class file loaded in operation is comprehensively analyzed, in order to find the class that potentially conflicts in time, and then avoid it is unnecessary
Application program run-time error, improve application program operation stability.
Description of the drawings
To describe the technical solutions in the embodiments of the present invention more clearly, make required in being described below to embodiment
Attached drawing is briefly described, it should be apparent that, the accompanying drawings in the following description is only some embodiments of the present invention, for
For those of ordinary skill in the art, without creative efforts, it can also be obtained according to these attached drawings other
Attached drawing.
Fig. 1 is an embodiment flow diagram of JavaEE applications class load conflict analysis method of the present invention；
Fig. 2 is the flow chart of another embodiment of JavaEE applications class load conflict analysis method of the present invention；
Fig. 3 is the structure diagram of the Classloader chain in above-described embodiment；
Fig. 4 is an example structure schematic diagram of JavaEE applications class load conflict analytical equipment of the present invention；
Fig. 5 is another example structure schematic diagram of JavaEE applications class load conflict analytical equipment of the present invention.
Specific embodiment
Below in conjunction with the attached drawing in the embodiment of the present invention, the technical solution in the embodiment of the present invention is carried out clear, complete
Site preparation describes, it is clear that described embodiment is only part of the embodiment of the present invention, instead of all the embodiments.It is based on
Embodiment in the present invention, those of ordinary skill in the art are obtained all other without making creative work
Embodiment shall fall within the protection scope of the present invention.
As shown in Figure 1, the embodiment of the present invention provides a kind of JavaEE applications class load conflict analysis method, the method packet
It includes：
S11, the corresponding Classloader chain of application to be analyzed is obtained.
S12, based on the Classloader chain, all non-duplicate class files of the application to be analyzed are carried out with conflict point
Analysis, to determine potential conflict class.
JavaEE applications class load conflict analysis method provided in an embodiment of the present invention obtains the corresponding class of application to be analyzed
Loader chain；Based on the Classloader chain, conflict analysis is carried out to all non-duplicate class files of the application to be analyzed, with
Determine potential conflict class.Compared with prior art, the Classloader chain can be based on, is realized to JavaEE application programs
The class file loaded in operation is comprehensively analyzed, in order to find the class that potentially conflicts in time, and then avoid it is unnecessary
Application program run-time error, improve application program operation stability.
As shown in Fig. 2, the embodiment of the present invention provides a kind of JavaEE applications class load conflict analysis method, the method packet
It includes：
S21, the deployment scenario for judging application to be analyzed if the application to be analyzed is application deployment, perform step
S22 and S23；If the application to be analyzed is non-application deployment, step S24 is performed.
S22, Classloader is applied according to the name acquiring of the application to be analyzed is corresponding.
S23, the corresponding Classloader chain of the application to be analyzed is obtained based on the application Classloader, and entered step
S27。
S24, it is created for the application to be analyzed using Classloader.
S25, all class files that the application to be analyzed includes are obtained according to the physical address of the application to be analyzed, and
All class files are added in the class load path using Classloader of the establishment.
S26, public Classloader is obtained, and set the application class of the establishment according to the interface that JavaEE servers provide
The parent loader of loader is the public Classloader, to obtain the corresponding Classloader of acquisition application to be analyzed
Chain.
Wherein, the common class is loaded as father's loader of all application deployment in the JavaEE servers.
The Classloader chain that S27, analyzing step S23 or S26 are obtained, to obtain all classes on the Classloader chain
Class file included in the class load path of loader and the class load path.
S28, duplicate removal processing is carried out to class file included in the class load path, to obtain the application to be analyzed
Comprising all non-duplicate class files.
Optionally, if being file in the class load path, institute in the class load path is obtained in a recursive manner
Include class file；If being jar file in the class load path, obtained in a manner of decompressing included in the class load path
Class file.
S29, for all non-duplicate class files, the class loading road of all Classloaders in the Classloader chain
Search operation is carried out in diameter, to obtain the potential conflict class and corresponding conflicting information, and to the potential conflict class
It is marked.
Wherein, the conflict class is the non-duplicate class file that can be found at least two class load paths, described
Conflicting information can be loaded including the conflict class by which Classloader and the conflict class can be from which class file
Loading.
It can be seen that JavaEE applications class load conflict analysis method provided in an embodiment of the present invention is added based on a class
Device chain is carried, class load conflict analysis is carried out to all non-duplicate class files that application to be analyzed includes, to determine potential conflict
Class.Wherein, the structure of the Classloader chain is as shown in figure 3, from the figure 3, it may be seen that all non-for being included to application to be analyzed
Repeat class file, the class loading of class load path, JavaEE server categories loader 32 in JavaEE applications Classloader 31
Class load conflict analysis is carried out in the class load path of three Classloaders that path and Java Virtual Machine provide, it is potential to determine
Conflict class, wherein three Classloaders be respectively JavaEE systems Classloader 33, JavaEE extension Classloader 34
Classloader 35 is guided with JavaEE.Compared with prior art, the Classloader chain can be based on, realizing should to JavaEE
The class file loaded in being run with program is comprehensively analyzed, and in order to find the class that potentially conflicts in time, and then is avoided
Unnecessary application program run-time error improves the stability of application program operation.
In addition, the embodiment of the present invention uses unified processing mode for application deployment and non-application deployment, so as to letter
The complexity of specific implementation is changed.
As shown in figure 4, the embodiment of the present invention provides a kind of JavaEE applications class load conflict analytical equipment, described device packet
Include Classloader administrative unit 41 and class load conflict analytic unit 42.
Wherein, the Classloader administrative unit 41, for obtaining the corresponding Classloader chain of application to be analyzed；
The class load conflict analytic unit 42, for being based on the Classloader chain, to the institute of the application to be analyzed
There is non-duplicate class file to carry out conflict analysis, to determine potential conflict class.
JavaEE applications class load conflict analytical equipment provided in an embodiment of the present invention obtains the corresponding class of application to be analyzed
Loader chain；Based on the Classloader chain, conflict analysis is carried out to all non-duplicate class files of the application to be analyzed, with
Determine potential conflict class.Compared with prior art, the Classloader chain can be based on, is realized to JavaEE application programs
The class file loaded in operation is comprehensively analyzed, in order to find the class that potentially conflicts in time, and then avoid it is unnecessary
Application program run-time error, improve application program operation stability.
As shown in figure 5, the embodiment of the present invention provides a kind of JavaEE applications class load conflict analytical equipment, described device packet
Include Classloader administrative unit 51, centralized control unit 52, document handling unit 53 and class load conflict analytic unit 54.
The Classloader administrative unit 51, for obtaining the corresponding Classloader chain of application to be analyzed.
Specifically, if the application to be analyzed is application deployment, the Classloader administrative unit 51, for working as
When the application to be analyzed is application deployment Classloader is applied according to the name acquiring of the application to be analyzed is corresponding；Base
The corresponding Classloader chain of the application to be analyzed is obtained in the application Classloader.
If the application to be analyzed is application deployment, the Classloader administrative unit 51, for be treated point when described
Analysis application is is that the application to be analyzed is created using Classloader during non-application deployment；According to the physics of the application to be analyzed
Address obtains all class files that the application to be analyzed includes, and all class files are added to the application of the establishment
In the class load path of Classloader；Public Classloader is obtained, and described in setting according to the interface that JavaEE servers provide
The parent loader using Classloader of establishment is the public Classloader, is corresponded to obtaining the acquisition application to be analyzed
Classloader chain.
Wherein, the common class is loaded as father's loader of all application deployment in the JavaEE servers.
The centralized control unit 52, for coordinating the Classloader administrative unit 51, the document handling unit 53
And the class.path inspection unit 54 carries out class load conflict analysis, and finishing analysis result and returns the analysis result
Back to caller.
Wherein, the analysis result includes potential conflict class and corresponding conflicting information.
The document handling unit 53 for parsing the Classloader chain, owns to obtain on the Classloader chain
Class file included in the class load path of Classloader and the class load path；And to institute in the class load path
Comprising class file carry out duplicate removal processing, to obtain all non-duplicate class files that the application to be analyzed includes.
Specifically, when in the class load path being file, the document handling unit 53 obtains in a recursive manner
Class file included in the class load path；When in the class load path be jar file when the document handling unit 53
Class file included in the class load path is obtained in a manner of decompressing.
The class load conflict analytic unit 54, for being directed to all non-duplicate class files, in the Classloader
Search operation is carried out in the class load path of all Classloaders in chain, to obtain the potential conflict class and corresponding conflict
Information, and the potential conflict class is marked.
Wherein, the conflict class is the non-duplicate class file that can be found at least two class load paths, described
Conflicting information can be loaded including the conflict class by which Classloader and the conflict class can be from which class file
Loading.
JavaEE applications class load conflict analytical equipment provided in an embodiment of the present invention is to be based on a Classloader chain, right
All non-duplicate class files that application to be analyzed includes carry out class load conflict analysis, to determine potential conflict class.With it is existing
Technology is compared, and can be based on the Classloader chain, realizes that the class file loaded in being run to JavaEE application programs carries out
It comprehensively analyzes, in order to find the class that potentially conflicts in time, and then avoids unnecessary application program run-time error, improve
The stability of application program operation.
In addition, the embodiment of the present invention uses unified processing mode for application deployment and non-application deployment, so as to letter
The complexity of specific implementation is changed.
One of ordinary skill in the art will appreciate that realizing all or part of flow in above-described embodiment method, being can be with
Relevant hardware is instructed to complete by computer program, the program can be stored in a computer read/write memory medium
In, the program is when being executed, it may include such as the flow of the embodiment of above-mentioned each method.Wherein, the storage medium can be magnetic
Dish, CD, read-only memory（Read-Only Memory, ROM）Or random access memory（Random Access
Memory, RAM）Deng.
The above description is merely a specific embodiment, but protection scope of the present invention is not limited thereto, any
Those familiar with the art in the technical scope disclosed by the present invention, all should by the change or replacement that can be readily occurred in
It is included within the scope of the present invention.Therefore, protection scope of the present invention should be subject to the protection scope in claims.
Claims (10)
1. a kind of JavaEE applications class load conflict analysis method, which is characterized in that the method includes：
Obtain the corresponding Classloader chain of application to be analyzed, the Classloader chain include JavaEE applications Classloader,
JavaEE server categories loader and the JavaEE systems Classloader of Java Virtual Machine offer, JavaEE extension Classloaders
Classloader is guided with JavaEE；
If the application to be analyzed is non-application deployment, the corresponding Classloader chain of application to be analyzed that obtains includes：For
The application to be analyzed is created using Classloader；The application to be analyzed is obtained according to the physical address of the application to be analyzed
Comprising all class files, and all class files are added to the class load path using Classloader of the establishment
In；Public Classloader is obtained according to the interface that JavaEE servers provide, and set the establishment using Classloader
Parent loader is the public Classloader, to obtain the corresponding Classloader chain of acquisition application to be analyzed, wherein, institute
State father loader of the public Classloader for all application deployment in the JavaEE servers；
Based on the Classloader chain, conflict analysis is carried out to all non-duplicate class files of the application to be analyzed, to determine
Potential conflict class.
If 2. according to the method described in claim 1, it is characterized in that, the application to be analyzed be application deployment, it is described
The corresponding Classloader chain of application to be analyzed is obtained to include：
Classloader is applied according to the name acquiring of the application to be analyzed is corresponding；
The corresponding Classloader chain of the application to be analyzed is obtained based on the application Classloader.
3. according to the method described in claim 1, it is characterized in that, described based on the Classloader chain, treated point to described
All non-duplicate class files of analysis application carry out conflict analysis, before determining potential conflict class, to further include：
The Classloader chain is parsed, to obtain the class load path of all Classloaders and the class on the Classloader chain
Class file included in load path；
Duplicate removal processing is carried out to class file included in the class load path, to obtain the institute that the application to be analyzed includes
There is non-duplicate class file.
4. according to the method described in claim 3, it is characterized in that, described obtain class text included in the class load path
Part includes：
If being file in the class load path, class text included in the class load path is obtained in a recursive manner
Part；
If being jar file in the class load path, class text included in the class load path is obtained in a manner of decompressing
Part.
5. method according to any one of claims 1 to 4, which is characterized in that it is described based on the Classloader chain, to institute
All non-duplicate class files for stating application to be analyzed carry out conflict analysis, to determine that potential conflict class includes：
For all non-duplicate class files, carried out in the class load path of all Classloaders in the Classloader chain
Search operation to obtain the potential conflict class and corresponding conflicting information, and is marked the potential conflict class；
Wherein, the conflict class is the non-duplicate class file that can be found at least two class load paths, the conflicting information
It can be loaded including the conflict class by which Classloader and the conflict class can be loaded from which class file.
6. a kind of JavaEE applications class load conflict analytical equipment, which is characterized in that it is single that described device includes Classloader management
Member, class load conflict analytic unit, wherein,
The Classloader administrative unit, for obtaining the corresponding Classloader chain of application to be analyzed, the Classloader chain packet
Include the JavaEE systems class loading that JavaEE applications Classloader, JavaEE server categories loader and Java Virtual Machine provide
Device, JavaEE extension Classloaders and JavaEE guiding Classloaders；
The Classloader administrative unit, be additionally operable to when the application to be analyzed be non-application deployment when be the application to be analyzed
It creates using Classloader；All classes text included according to the physical address of the application to be analyzed acquisition application to be analyzed
Part, and all class files are added in the class load path using Classloader of the establishment；It is taken according to JavaEE
The interface that business device provides obtains public Classloader, and set the establishment is described using the parent loader of Classloader
Public Classloader, to obtain the corresponding Classloader chain of acquisition application to be analyzed, wherein, the public Classloader is
Father's loader of all application deployment in the JavaEE servers；
The class load conflict analytic unit, for being based on the Classloader chain, to all non-heavy of the application to be analyzed
Multiple class file carries out conflict analysis, to determine potential conflict class.
7. device according to claim 6, which is characterized in that the Classloader administrative unit, for be treated point when described
When analysis application is application deployment Classloader is applied according to the name acquiring of the application to be analyzed is corresponding；It is answered based on described
The corresponding Classloader chain of the application to be analyzed is obtained with Classloader.
8. device according to claim 6, which is characterized in that described device further includes document handling unit, wherein, it is described
Document handling unit, document handling unit, for parsing the Classloader chain, to obtain all classes on the Classloader chain
Class file included in the class load path of loader and the class load path；To included in the class load path
Class file carries out duplicate removal processing, to obtain all non-duplicate class files that the application to be analyzed includes.
9. device according to claim 8, which is characterized in that the document handling unit, for working as the class loading road
Class file included in the class load path is obtained in a recursive manner when being file in diameter；When being in the class load path
Class file included in the class load path is obtained during jar file in a manner of decompressing.
10. according to claim 6 to 9 any one of them device, which is characterized in that the class load conflict analytic unit is used
In for all non-duplicate class files, looked into the class load path of all Classloaders in the Classloader chain
Operation is looked for, to obtain the potential conflict class and corresponding conflicting information, and the potential conflict class is marked,
In, the conflict class is the non-duplicate class file that can be found at least two class load paths, the conflicting information packet
Include it is described conflict class can be loaded by which Classloader and it is described conflict class can be loaded from which class file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510121221.9A CN104699547B (en) | 2015-03-19 | 2015-03-19 | JavaEE applications class load conflict analysis method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510121221.9A CN104699547B (en) | 2015-03-19 | 2015-03-19 | JavaEE applications class load conflict analysis method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104699547A CN104699547A (en) | 2015-06-10 |
| CN104699547B true CN104699547B (en) | 2018-06-26 |
Family
ID=53346708
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510121221.9A Active CN104699547B (en) | 2015-03-19 | 2015-03-19 | JavaEE applications class load conflict analysis method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104699547B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106933611B (en) * | 2015-12-31 | 2020-04-28 | 北京五八信息技术有限公司 | Class loading method and class loader |
| CN105718282A (en) * | 2016-01-05 | 2016-06-29 | 山东中创软件工程股份有限公司 | Method and device for handling class conflict problem |
| CN106201592A (en) * | 2016-06-29 | 2016-12-07 | 北京小米移动软件有限公司 | A kind of method and apparatus searching class |
| CN106874060B (en) * | 2017-01-16 | 2020-12-18 | 吴建伟 | Method and equipment for judging whether JAR package is quoted |
| CN108595337A (en) * | 2018-05-07 | 2018-09-28 | 杭州有赞科技有限公司 | A kind of operation method and system of Jar packets |
| CN113448858A (en) * | 2021-07-09 | 2021-09-28 | 北京三快在线科技有限公司 | Class conflict detection method, device, equipment and readable storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101000552A (en) * | 2007-01-15 | 2007-07-18 | 华为技术有限公司 | Java kind loading method and loader |
| CN101105757A (en) * | 2007-08-31 | 2008-01-16 | 金蝶软件（中国）有限公司 | Class loading separation method and class loading separation device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4881023B2 (en) * | 2006-02-01 | 2012-02-22 | キヤノン株式会社 | Information processing apparatus, method for executing object-oriented program in the apparatus, and program therefor |
-
2015
- 2015-03-19 CN CN201510121221.9A patent/CN104699547B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101000552A (en) * | 2007-01-15 | 2007-07-18 | 华为技术有限公司 | Java kind loading method and loader |
| CN101105757A (en) * | 2007-08-31 | 2008-01-16 | 金蝶软件（中国）有限公司 | Class loading separation method and class loading separation device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104699547A (en) | 2015-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104699547B (en) | JavaEE applications class load conflict analysis method and device | |
| KR102077360B1 (en) | Generating native code from intermediate language code for an application | |
| US9942307B2 (en) | Web application script migration | |
| US8615750B1 (en) | Optimizing application compiling | |
| US8904368B2 (en) | Instantiating a composite application for different target platforms | |
| EP1445693B1 (en) | System and method for building and configuring cross-platform applications | |
| US10209968B2 (en) | Application compiling | |
| US7882492B2 (en) | Intelligent computer program debugger, and system and method for implementing the same | |
| US9858094B2 (en) | Monitoring and actuation of view controller parameters to reach deep states without manual developer intervention | |
| EP2386953A1 (en) | Systems and methods for generating reusable test components out of remote application programming interface | |
| US20100083225A1 (en) | Dynamic Autocompletion Tool | |
| US20130091418A1 (en) | Cross-browser toolbar and method thereof | |
| CN102982169A (en) | Browser and method for isolating webpage plugins | |
| CN111984357A (en) | Resource loading method, device and equipment based on WebWorker and storage medium | |
| US6681266B2 (en) | Late binding dynamic software configuration information | |
| US20130254758A1 (en) | Application Construction for Execution on Diverse Computing Infrastructures | |
| US8935402B2 (en) | Resource launch from application within application container | |
| US9639375B2 (en) | Generation of language bindings for libraries using data from compiler generated debug information | |
| US7428729B2 (en) | Methods, systems, and computer program products for integrating legacy applications into a platform-independent environment | |
| US20090049423A1 (en) | Javascripttm programming extension | |
| US11221844B2 (en) | Automated application partitioning system | |
| KR20180058579A (en) | Method for generating a test senario based on activity stack | |
| US9389838B2 (en) | Method for creating a computer software compiler for client server computing | |
| US20100100873A1 (en) | Instrumentation of Computer-Based Application Software | |
| US20130081007A1 (en) | Providing continuous application availability during application update |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |