How It Works Directory Structure
4.6.1 How It Works
The files placed in the AppFileOverrides subdirectory are staged and distributed along with the rest of the plan directory contents and are available on all of the targets. Applications are then able to load these files as resources using the current classloader for example, using the ClassLoader.getResourceAsStream method. This either finds the overridden files or the files packaged in the application, depending on the configuration and whether overridden files are supplied. For Web applications, application file overrides only apply to the classpath related resources which are in WEB-INFclasses and WEB-INFlib, and do not apply to the resource path for the Web application. Therefore, overrides are seen by Web applications using the classloader.getResourceAsStream method to lookup resources, but overrides do not affect Web application calls to the ServletContext.getResourceAsStream method. In order to use this feature, you must: ■ Specify a plan for the deployment see Section 4.3, Creating a New Deployment Plan to Configure an Application . ■ Specify the config-root within in the plan. ■ Provide a config-rootAppFileOverrides subdirectory.4.6.2 Directory Structure
The contents of the AppFileOverrides subdirectory use the existing plan directory structure and directory naming conventions that already exist for descriptor overrides. For more information on directory naming conventions, see Section 3.1, Packaging Files for Deployment . Enabling application file overrides causes a directory ClassFinder to be added to the application and module level classloaders, which point to the appropriate root directories within the AppFileOverrides subdirectory which is in the plan directory. The ClassFinder inserted into the front of the applications classloader is given a structure of AppDeploymentMBean.getLocalPlanDir + separator + AppFileOverrides. The ClassFinder inserted into the front of the modules classloaders is given a structure of AppDeploymentMBean.getLocalPlanDir + separator + AppFileOverrides + separator + moduleURI. For Example:4.6.3 Application Usage
Parts
» Oracle Fusion Middleware Online Documentation Library
» Document Scope and Audience Guide to This Document
» Standards Compatibility Deployment Terminology
» Related Documentation New and Changed Features in This Release
» Overview of the Deployment Process Java EE 5 Deployment Implementation
» Enterprise Application Web Application Enterprise JavaBean Resource Adapter
» Web Service J2EE Library Optional Package
» JDBC, JMS, and WLDF Modules Client Application Archive
» weblogic.Deployer Administration Console WLST Deployment Tools for Developers
» Understanding Default Deployment Names Understanding Application Naming Requirements
» Steps for Creating an Application Installation Directory
» How FastSwap Deployment Works Supported FastSwap Application Configurations
» Enabling FastSwap In Your Application Application Types and Changes Supported with FastSwap
» Limitations When Using FastSwap
» Understanding Deployment Version Strings Best Practices for Preparing Deployment Files
» Deployment Configuration Life Cycle
» Understanding Application Deployment Descriptors Understanding WebLogic Server Deployment Plans
» Benefits of a Single Deployment Plan Workflow Single Deployment Plan Ownership and Limitations
» Benefits of a Multiple Deployment Plan Workflow Multiple Deployment Plan Ownership and Limitations
» Understanding Deployment Plan Contents
» Using an Existing Deployment Plan to Configure an Application
» How It Works Directory Structure
» Additional Configuration Tasks Best Practices for Managing Application Configuration
» Goals for Exporting a Deployment Configuration Tools for Exporting a Deployment Configuration
» Understanding Deployment Property Classifications
» Steps for Exporting an Applications Deployment Configuration Staging Application Files for Export
» Generating a Template Deployment Plan using weblogic.PlanGenerator
» Overview of Common Deployment Scenarios
» Deploying to a Single-Server Domain Deploying an Application with a Deployment Plan
» Understanding Deployment Targets Deploying to One or More Targets
» Deploying to a Cluster Target Enforcing Consistent Deployment to All Configured Cluster Members
» Module-Targeting Syntax Targeting Web Application Modules
» Staging Mode Descriptions and Best Practices
» Using Nostage Mode Deployment Syntax for Nostage Mode Using Stage Mode Deployment
» Syntax for Stage Mode Using External_stage Mode Deployment Syntax for external_stage Mode
» Understanding Deployment Behavior for Shared Libraries
» Registering Libraries with WebLogic Server Specifying Library Versions at Deployment
» Production Redeployment Overview of Redeployment Strategies
» Limitations of Auto-Deployment Understanding When to Use Different Redeployment Strategies
» How Production Redeployment Works
» Development Requirements Requirements and Restrictions for Production Redeployment
» Steps for Distributing a New Version of an Application Making an Application Available to Clients
» Redeploying Applications and Modules In-Place
» Stopping an Application to Restrict Client Access
» Undeploying an Application or Module
Show more