Plug-in loading frame for WEB application in field of JavaEE and method

Abstract

The invention discloses a plug-in loading frame for WEB application in the field of JavaEE and a method. The plug-in loading frame comprises a plug-in packet checking preparation module, a plug-in packet decompression processing module and a resource loading module, wherein the plug-in packet checking preparation module is used for checking a standard format of a plug-in PAR packet, and used for calculating and recording the abstract of the plug-in PAR packet; the plug-in packet decompression processing module is used for decompressing a current plug-in PAR packet into an appointed temporary catalog when the current plug-in PAR packet needs to be decompressed; the resource loading module is used for implementing resource file movement operation and dynamic loading operation through a loader corresponding to each type of resource files when a WEB application is started. Therefore, by abstracting a management unit, namely, the plug-in Par packet, which is smaller than a standard WebApp and comprises various WEB resources, and by providing the loading frame of the plug-in Par packet, a modulation management mode which is simple and convenient inside the WebApp can be achieved in a simple and convenient mode.

Description

technical field [0001] The present invention relates to the technical field of JavaEE, and more specifically, relates to a plug-in loading framework and method for WEB applications in the JavaEE field. Background technique [0002] The traditional integrated development and management method of large-scale WEB application systems, that is, the entire WEB application is one project, unified integration and release, and unified version management will lead to low efficiency and low success rate in the integration stage, and in the group management of personnel, as well as engineering The management of aspects such as authority assignment and code is complex. For the development and management of WEB application systems in the JavaEE field, the industry generally has several options to solve the above problems. The first is a relatively heavyweight solution, which is to adopt a distributed service architecture + single sign-on mechanism. The second approach is to use EAR (Ente...

AI Technical Summary

Problems solved by technology

[0004] The biggest disadvantage of adopting the second EAR integration method is the restriction on the middleware. Since the EJB module is allowed to be included in the EAR specification, it cannot run in the ordinary Servlet container. For example, the Tomcat middleware does not support the EAR specification, which leads to Many products cannot use EAR integration

[0005] Adopting the third Servlet 3.0 specification pluggability solution also has two limitations. One is that this mechanism requires a corresponding version of middleware that supports the Servlet 3.0 specification. For example, Tomcat requires version 7.0 or above, and Weblogic requires 12c The above version, but there are still many applications in the industry based on Servlet2.3 and later specifications, especially many e-government applications

The second is that it can only perform plug-in management for the content defined in web.xml and the resources that carry these contents, while for other WEB resources, such as page resources (including html\js\css\jpg, etc.), third-party jar Packages, etc. do not support plug-in group management

Images