Shared Web Module Logical Merging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mechanisms for sharing web modules in J2EE environments are inefficient, requiring explicit copying and duplication of code and configurations across multiple web modules, leading to storage inefficiencies and increased maintenance efforts due to the lack of a mechanism for sharing common resources.
Innovation Solution
A system and method for logically merging shared web modules with a primary web module, utilizing a shared web module designation file to identify and prioritize shared modules, which are then automatically merged with the web application at runtime, reducing the need for multiple copies and simplifying maintenance by propagating changes centrally.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If common code and configuration are explicitly copied into each web module, then each web module can function independently, but storage efficiency deteriorates and maintenance complexity increases
Solution Approach 1:
The patent merges common web module components into a shared archive that can be referenced by multiple web modules. Instead of duplicating code and configuration across separate modules, the system combines these common elements into a single shared resource that multiple modules can access, thereby improving storage efficiency while maintaining functional independence through logical merging at runtime.
Solution Approach 2:
The shared web module archive serves multiple functions: it stores common code, configuration files, and resources that can be reused across different web modules. This universal archive structure allows a single storage location to support multiple web applications, eliminating the need for separate copies and reducing overall storage requirements while maintaining module independence.
2Ease of manufacture
If common code and configuration are explicitly copied into each web module, then each web module can be deployed independently, but maintenance effort increases due to propagation requirements
Solution Approach 1:
The patent merges common web module components into a shared archive that can be referenced by multiple web modules. Instead of duplicating code and configuration across separate modules, the system combines these common elements into a single shared resource that multiple modules can access, thereby improving storage efficiency while maintaining functional independence through logical merging at runtime.
Solution Approach 2:
The system creates a logical copy mechanism where web modules reference common components in a shared archive rather than containing physical copies. This allows deployment independence since each module can be deployed separately, but maintenance is simplified because changes to common components in the shared archive are automatically reflected in all referencing modules without manual propagation.
3Loss of substance
If web modules share common resources through a shared archive, then storage efficiency improves, but device complexity increases due to merging mechanisms
Solution Approach 1:
The patent introduces a shared archive as an intermediary structure between multiple web modules and common resources. This intermediary layer manages the complexity of resource sharing by providing a standardized interface for modules to access common code, configuration, and assets. The application server acts as another intermediary that handles the logical merging process, thereby managing system complexity while enabling efficient resource sharing.
Solution Approach 2:
The system performs preliminary organization of common web module components into a shared archive during the deployment phase. By pre-structuring the shared resources and establishing reference relationships before runtime, the system reduces the complexity of the merging operation during execution. The shared module designation files and archive structures are prepared in advance, simplifying the runtime merging process.
4Loss of time
If web modules share common resources through a shared archive, then maintenance effort reduces through centralized changes, but ease of operation deteriorates due to configuration complexity
Solution Approach 1:
The patent introduces a shared archive as an intermediary structure between multiple web modules and common resources. This intermediary layer manages the complexity of resource sharing by providing a standardized interface for modules to access common code, configuration, and assets. The application server acts as another intermediary that handles the logical merging process, thereby managing system complexity while enabling efficient resource sharing.
Solution Approach 2:
The system implements self-service mechanisms where the application server automatically performs the logical merging of shared web modules with individual web modules at runtime. The shared module designation files contain metadata that enables automatic identification and merging of common components. This automation reduces manual configuration effort and simplifies operations, as the system self-manages the complex merging process without requiring manual intervention for each web module.
Data Source
AI summary
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.