Split-Source Directory Structure for Virtual Path Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional software development approaches using Enterprise Archive (EAR) files are inconvenient for application development, as they mix source files and system-generated output, making it difficult to maintain a clean build and requiring mirroring of the EAR structure, which limits flexibility and prevents web-editing-in-place functionality.
Innovation Solution
A split-source directory structure is introduced, separating source and output directories, allowing the server to view both, with an abstraction layer and virtual mappings that map physical to virtual locations, enabling flexible build structures and eliminating the need for file copying during the build process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If a traditional EAR structure is used for application development, then the application can be packaged and deployed, but the source files and system-generated output are mixed together, making it difficult to maintain a clean build and perform iterative development
Solution Approach 1:
The patent divides the application directory into separate source and build directories. The source directory contains only human-readable source files under version control, while the build directory contains generated files. This segmentation allows developers to maintain a clean separation between source and generated content, enabling easy iterative development without mixing file types.
Solution Approach 2:
The patent extracts the generated files from the source directory and places them in a separate build directory. This extraction removes the harmful mixing of source and generated files, allowing the source directory to remain clean and manageable while the build directory handles all system-generated output.
2Adaptability or versatility
If the build structure mirrors the EAR structure, then deployment is simplified, but flexibility in layout is reduced and web-editing-in-place functionality is prevented
Solution Approach 1:
The patent introduces a virtual file system layer that acts as an intermediary between the physical directory structure and the EAR structure. This virtual layer maps logical paths to physical locations, allowing the build structure to be laid out flexibly for development purposes while automatically translating to the required EAR structure for deployment, thus maintaining both flexibility and ease of deployment.
3Device complexity
If source files and generated files are in the same directory, then the directory structure is simple, but it becomes confusing and difficult to delete only system-generated files
Solution Approach 1:
The patent segments the directory structure into distinct source and build directories. The source directory contains only editable source files, while the build directory contains all system-generated files. This segmentation maintains relative simplicity while enabling easy deletion of generated files by simply removing the build directory contents without affecting source files.
Data Source
AI summary
A development-oriented split-source directory structure, that can be used with an application server and which solves a number of the problems associated with traditional Enterprise Archive (EAR) files. In particular, the split-source directory structure presents a clean separation between human-readable source files stored in a source control system and generated java class files. The two directories (source and output) appear like a single application. In addition, the split-source directory structure supports an abstraction layer and mappings that allow a physical file location to be mapped to a virtual location. In this manner, the system provides flexibility in how the build structure can be laid out for a particular application development.