System and method for providing shared web modules

• US 8,862,686 B2
• Filed: 08/28/2003
• Issued: 10/14/2014
• Est. Priority Date: 08/28/2003
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: McGee, Jason Robert, Morton, Michael John, Peters, Brent A.
• Primary Examiner(s): Keehn, Richard G
• Application Number:
  US10/650,894
• Publication Number:
  US 20050050155A1
• Time in Patent Office: 4,065 Days
• Field of Search: 709201-203, 709213-215, 709220-222
• US Class Current: 709/213
• CPC Class Codes: G06F 8/54 Link editing before load time
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system, apparatus, and method for sharing web modules amongst a plurality of other web applications are provided. Shared web modules are stored in an archive data structure for use with web applications. The web applications, and/or the web modules of the web applications, may include a designation file that identifies the shared web modules that are to be incorporated into the web modules for the web application. A runtime component selectively locates these shared web modules and logically merges them with the web modules of the web application according to precedence or priority of the shared web modules as designated by the shared web module designation file. The result is a logically merged web module that contains the shared web modules referenced in the shared web module designation file.

Claims

1. A method of generating a logically merged web application, comprising:

initializing a runtime environment for a web application;

during the initialization process of the runtime environment, determining whether the web application includes shared web modules that need to be logically merged with existing web modules of the web application, logically merged referring to a data structure defining the logically merged web application, the data structure combining both code of the existing web modules of the web application and also a copy of code of the shared web modules;

upon determining that the web application includes shared web modules that need to be logically merged, reading a shared module designation file of the web application and identifying the shared web modules to be merged along with their priorities, the shared module designation file including descriptors of shared web modules for logically merging with existing web modules of the web application, the descriptors identifying both a filename for each of the shared modules and also a priority for each of the shared web modules;

determining paths to the shared web modules and resolving any conflicts between web resources of the shared web modules using the identified priorities in the shared module designation file by determining the priority associated with each shared web module and resolving any conflicts in favor of one of the shared web modules having a higher priority than a different one of the shared web modules; and

,

logically merging the shared web modules with the existing web modules of the web application to generate a logically merged web application.

2. The method of claim 1, further comprising:

loading the logically merged web application into a web container.

3. The method of claim 2, wherein the container uses one or more application program interfaces (APIs) to identify paths to the shared web modules and loads the shared web modules when loading the logically merged web application.

4. The method of claim 1, wherein the web application is an enterprise archive (EAR) and wherein the logically merged web application is a logically merged EAR.

5. The method of claim 1, wherein the shared web modules includes at least one of a web archive (WAR) file, an enterprise java bean (EJB) archive file, and a resource archive (RAR) file.

6. The method of claim 1, wherein logically merging the shared web modules with the existing web modules of the web application includes using a service provider interface (SPI) that provides merge logic for merging different module types.

7. The method of claim 1, wherein logically merging the shared web modules with the existing web modules of the web application includes at least one of relinking references to the shared web modules in the web modules of the web application, extrapolating policy information for the shared web modules from a policy file associated with the web application, and modifying a class path for the web application to include paths to each of the shared web modules.

8. The method of claim 1, wherein the shared module designation file is one of a separate file that is stored as part of a parent web module file, at least one of bindings and extensions in the parent web module file, a part of the parent web module web.xml file, a separate file in a web application enterprise archive (EAR) file, at least one of bindings and extensions in the web application file, and a part of a web application application.xml file.

9. A computer program product in a computer readable storage device for generating a logically merged web application, comprising:

computer executable instructions for initializing a runtime environment for a web application;

computer executable instructions for, during the initialization process of the runtime environment, determining whether the web application includes shared web modules that need to be logically merged with existing web modules of the web application, logically merged referring to a data structure defining the logically merged web application, the data structure combining both code of the existing web modules of the web application and also a copy of code of the shared web modules;

computer executable instructions for, upon determining that the web application includes shared web modules that need to be logically merged, reading a shared module designation file of the web application and identifying the shared web modules to be merged along with their priorities, the shared module designation file including descriptors of shared web modules for logically merging with existing web modules of the web application, the descriptors identifying both a filename for each of the shared modules and also a priority for each of the shared web modules;

computer executable instructions for determining paths to the shared web modules and resolving any conflicts between web resources of the shared web modules using the identified priorities in the shared module designation file by determining the priority associated with each shared web module and resolving any conflicts in favor of one of the shared web modules having a higher priority than a different one of the shared web modules; and

,

computer executable instructions for logically merging the shared web modules with the existing web modules of the web application to generate a logically merged web application.

10. The computer program product of claim 9, further comprising:

computer executable instructions for loading the logically merged web application into a web container.

11. The computer program product of claim 10, wherein the container uses one or more application program interfaces (APIs) to identify a path to each shared web module.

12. The computer program product of claim 9, wherein the computer executable instructions for logically merging the web modules of the web application include computer executable instructions for using a service provider interface (SPI) that provides merge logic for merging different module resources.

13. The computer program product of claim 9, wherein the computer executable instructions for logically merging the shared web modules with the existing web modules of the web application include computer executable instructions for relinking references to the web modules of the web application, computer executable instructions for extrapolating policy information for the shared web modules from a policy file associated with the web application, and computer executable instructions for modifying a class path for the web application to include paths to each of the shared web modules.

14. The computer program product of claim 9, wherein the shared module designation file is one of a separate file that is stored as part of a parent web module file, at least one of bindings and extensions in the parent web module file, a part of the parent web module web.xml file, a separate file in a web application enterprise archive (EAR) file, at least one of bindings and extensions in the web application file, and a part of a web application application.xml file.

15. An apparatus for generating a logically merged web module for a web application, comprising:

a system bus;

a local memory connected to the system bus, wherein the memory contains computer executable instructions;

a processor connected to the system bus, wherein the processor executes the computer executable instructions to direct the apparatus to;

initialize a runtime environment for a web application;

during the initialization process of the runtime environment, determine whether the web application includes shared web modules that need to be logically merged with existing web modules of the web application, logically merged referring to a data structure defining the logically merged web application, the data structure combining both code of the existing web modules of the web application and also a copy of code of the shared web modules;

upon determining that the web application includes shared web modules that need to be logically merged, read a shared module designation file of the web application and identifying the shared web modules to be merged along with their priorities, the shared module designation file including descriptors of shared web modules for logically merging with existing web modules of the web application, the descriptors identifying both a filename for each of the shared modules and also a priority for each of the shared web modules;

determine paths to the shared web modules and resolving any conflicts between web resources of the shared web modules using the identified priorities in the shared module designation file by determining the priority associated with each shared web module and resolving any conflicts in favor of one of the shared web modules having a higher priority than a different one of the shared web modules; and

,

logically merge the shared web modules with the existing web modules of the web application to generate a logically merged web application.

16. The computer program product of claim 15, wherein the processor further executes the computer executable instructions to direct the apparatus to load the logically merged web application into a web container.

17. The apparatus of claim 15, wherein the shared module designation file is one of a separate file that is stored as part of a parent web module file, at least one of bindings and extensions in the parent web module file, a part of the parent web module web.xml file, a separate file in a web application enterprise archive (EAR) file, at least one of bindings and extensions in the web application file, and a part of a web application application.xml file.