Oracle JHeadstart Developer's Guide - Downloads - Oracle

• Generate all Main faces-config files in the WEB-INF directory with a suffix
indicating the service
• JhsCommon-beans.xml is shared by all services (application definitions); the
location should never be changed.
• Create a subdirectory per service for the generation of group beans faces
config files, pages and regions. Make a subdirectory under this “service”
directory for each of these file types.
• The View Package property should be the same across all services
• The Resource Bundle Type and NLS Resource Bundle properties should be
the same across all services.
Note that all service-level properties that are generally the same across all services have
got the same values as in your “own” application definition. If you later on decide to
make changes to these settings in your own application definition, then you will need to
make the same change in the MenuAdminAppDef Application Definition.
Now, if you are satisfied with the settings, you can run the JAG for the
MenuAdminAppDef. Note that like every other Application Definition service, the Menu
Admin service is treated as another module in your application: the generated SQL script
DynamicMenuDataMenuAdminService.sql has inserted a row in JHS_MODULES, and
rows in JHS_MENU_ITEMS for all level 1 and level 2 groups.
9.2.3. Defining the Menu Structure At Runtime
You are now ready to run the generated application, and change/define the menu
structure at runtime. If you start the application again, you will notice that the menu
structure is quite similar to the static menu structure.
This is because the generated SQL script that inserts rows in the JHS_MODULES and
JHS_MENU_ITEMS tables generates entries using the same algorithm as used for the
static menu structure. Now, using the module drop down list, we can navigate to the
MenuAdmin module, and change the menu structure anyway we want.
9 - 10 Generating Menu Structures JHeadstart Developer’s Guide