Source and Build Directories
3.1.1 Source and Build Directories
The source and build directories form the basis of the split development directory environment. The source directory contains all editable files for your project—Java source files, editable descriptor files, JSPs, static content, and so forth. You create the source directory for an application by following the directory structure guidelines described in Section 3.3, Organizing Java EE Components in a Split Development Directory . The top level of the source directory always represents an Enterprise application .ear file, even if you are developing only a single Java EE module. Subdirectories beneath the top level source directory contain: ■ Enterprise Application Modules EJBs and Web applications ■ Descriptor files for the Enterprise application application.xml and weblogic-application.xml ■ Utility classes shared by modules of the application for example, exceptions, constants ■ Libraries compiled.jar files, including third-party libraries used by modules of the application The build directory contents are generated automatically when you run the wlcompile ant task against a valid source directory. The wlcompile task recognizes EJB, Web application, and shared library and class directories in the source directory, and builds those components in an order that supports common class path requirements. Additional Ant tasks can be used to build Web Services or generate deployment descriptor files from annotated EJB code. Figure 3–1 Source and Build Directories The build directory contains only those files generated during the build process. The combination of files in the source and build directories form a deployable Java EE application. Note: The split development directory structure does not provide support for developing new Resource Adapter components. Creating a Split Development Directory Environment 3-3 The build and source directory contents can be place in any directory of your choice. However, for ease of use, the directories are commonly placed in directories named source and build, within a single project directory for example, \myproject\build and \myproject\source.3.1.2 Deploying from a Split Development Directory
Parts
» Oracle Fusion Middleware Online Documentation Library
» Document Scope and Audience WebLogic Server and the Java EE Platform
» Servlets JavaServer Pages Web Application Modules
» EJB Overview EJBs and WebLogic Server
» Java EE Programming Model Packaging and Deployment Overview
» Overview of Java EE Applications and Modules Connector Modules WebLogic Web Services
» Automatically Generating Deployment Descriptors EJBGen Java-based Command-line Utilities
» JMS and JDBC Modules Deployment Plans
» Source Code Editor or IDE Database System and JDBC Driver Web Browser
» Third-Party Software Development Software
» Basic Steps for Using wlserver Sample build.xml Files for wlserver
» What the wlconfig Ant Task Does
» Basic Steps for Using wlconfig wlconfig Ant Task Reference
» query invoke Nested Elements
» Source and Build Directories
» Deploying from a Split Development Directory Split Development Directory Ant Tasks
» Source Directory Overview Enterprise Application Configuration Web Applications
» EJBs Important Notes Regarding EJB Descriptors
» weblogic.BuildXMLGen Syntax Generating a Basic build.xml File Using weblogic.BuildXMLGen
» Organizing Libraries and Classes Shared by Multiple EARs
» Annotation Parsing Deployment View of Annotation Configuration Compiling Annotated Classes
» javax.annotation.PostConstruct javax.annotation.PreDestroy
» Java Classloader Hierarchy Loading a Class
» prefer-web-inf-classes Element Changing Classes in a Running Program
» Configuring Class Caching Java Classloading
» Overview of WebLogic Server Application Classloading Application Classloader Hierarchy
» Custom Module Classloader Hierarchies Declaring the Classloader Hierarchy
» Individual EJB Classloader for Implementation Classes
» Application Classloading and Pass-by-Value or Reference Using a Filtering Classloader
» What is a Filtering ClassLoader Configuring a FilteringClassLoader
» Resource Loading Order WebLogic Server Application Classloading
» About Resource Adapter Classes Packaging Shared Utility Classes Manifest Class-Path
» Using the Classloader Analysis Tool CAT
» Optional Packages Overview of Shared Java EE Libraries and Optional Packages
» Library Directories Versioning Support for Libraries
» Shared Java EE Libraries and Optional Packages Compared
» Assembling Shared Java EE Library Files
» Assembling Optional Package Class Files Editing Manifest Attributes for Shared Java EE Libraries
» Referencing Optional Packages from a Java EE Application or Module
» Web Application Shared Java EE Library Information Using WebApp Libraries With Web Applications
» Best Practices for Using Shared Java EE Libraries
» Understanding Application Life Cycle Events
» Example of Production Deployment Sequence When Using Application Version Life Cycle Events
» Programming Context Propagation: Main Steps Programming Context Propagation in a Client
» Programming Context Propagation in an Application
» Configuring JavaMail for WebLogic Server Sending Messages with JavaMail
» Reading Messages with JavaMail
Show more