Deployment Descriptor Builder for Web Application Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual editing of lengthy and cryptic XML deployment descriptor files for web applications is error-prone and prone to synchronization issues with application source files, leading to potential deployment errors.

Innovation Solution

An interactive tool, referred to as a 'builder,' allows users to edit deployment descriptors graphically, validating and generating new descriptors as needed, and automatically updates descriptors to reflect changes in application source files, using a GUI with a resource hierarchy and XML parser to manage deployment information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If deployment descriptor files are manually edited, then users can directly modify configuration information, but errors and synchronization issues occur

Engineering Contradiction:
ImproveDirect modification capabilityVSAvoidSynchronization accuracy
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a deployment descriptor editor as an intermediary tool between the user and the XML deployment descriptor files. This editor provides a graphical user interface that abstracts the complex XML structure, allowing users to modify deployment descriptors through form-based interfaces rather than direct text editing. The editor automatically generates and updates the corresponding XML files, ensuring synchronization between the application source files and deployment descriptors while maintaining ease of modification.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If XML deployment descriptor files are used, then comprehensive configuration information can be provided, but the files become lengthy and cryptic

Engineering Contradiction:
ImproveConfiguration completenessVSAvoidFile readability
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent segments the complex deployment descriptor information into organized hierarchical categories through the graphical editor interface. Instead of presenting users with a single lengthy XML file, the editor divides the configuration into logical sections such as application parameters, module configurations, security settings, and persistence information. Each section can be independently viewed and modified, making the comprehensive configuration information manageable and readable while preserving all necessary deployment details.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If manual editing is performed, then flexibility in modification is achieved, but time consumption increases

Engineering Contradiction:
ImproveModification flexibilityVSAvoidEditing efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements preliminary action by providing default deployment descriptor configurations that are automatically generated based on the application source files. When a new application is deployed, the editor pre-populates the deployment descriptor with appropriate default values and structures, eliminating the need for manual creation of each configuration element. Users can then selectively modify only the specific parameters that need customization, significantly reducing editing time while maintaining flexibility for targeted modifications.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7506327B2System and method for manipulating and automatically updating enterprise application deployment descriptors
Publication Date: 2009.03.17 ORACLE INT CORP
  • US7506327B2 patent drawing
  • US7506327B2 patent drawing
  • US7506327B2 patent drawing

AI summary

A system and method for updating at least one deployment descriptor, comprising creating a first representation of the at least one deployment descriptor; creating a second representation of a second at least one deployment descriptor based on one or more source files; comparing the first representation with the second representation; updating the first representation based on the second representation if the first representation is out-of-date; and wherein the method can be invoked from an integrated development environment.