Oracle JHeadstart Developer's Guide - Downloads - Oracle

2.3. Organizing JHeadstart Application Definition Files
As explained in chapter “Using JHeadstart Add-Ins”, the JHeadstart Application
Generator is driven the Application Definition file that holds the generator metadata.
Although the name of the file suggests that you create only one application definition file
for your entire application, we do recommned to create multiple application definition
files, unless your application is really small. A typical approach is to create one
application definition file for each logical subsystem. Since an application definition file
is based on one data control (Application Module), the structure of your application
definition files will typically follow the structure of your ADF BC application modules,
which in turn should map your subsystem structure.
2.3.1. Service Level Settings that Should Be the Same Accross Application Definitions
When you create multiple application definition files, you should be aware of the fact
that a number of settings you make at the service-level in the Application Definition
Editor, are really application-wide settings. In other words, some service-level settings
should be the same in all application definition file. Failing to keep these settings in
synch might result in unexpected errors when running the application. For example, if
the NLS resource bundle name property is different, then depending on the application
definition file last generated, some pages might not be able to find the translatable
strings, because they are in a different resource bundle, no longer configured for use in
JhsCommonBeans.xml.
Here is a list with the service-level settings that should be the same across all application
definition files:
• Generator Flavours: View Type and JSP Version
• File Locations: Common Beans Faces Config
• Java: View Package, Page Definitions SubPackage
• UI Settings: Date Format, DateTime Format
• Security: Authentication Type, Use Role-based Authorization, Authorization
Type, Authorize Using Group Permissions
• Internationalization: NLS Resource Bundle, Resource Bundle Type, Generator
Default Locale, Generator Locales, Read User Locale from, Generate Locale
Switcher
• Runtime Customizations: Allow Runtime Customization of Menu, Allow use of
Flex regions, Allow Runtime Customization of Items
2.3.2. Naming Conventions for File Location Properties
To cleanly organize the output produced by the JHeadstart Application Generator, it is
helpful to set naming conventions for the File Location properties thet can be set at the
service-level of an application definition file.
Here are suggested naming conventions.
Property Value
Main Faces Config /WEB-INF/faces-config-.xml
JHeadstart Developer's Guide Getting Started 2 - 11