GBC 4.01
Customization
How customization works
Planning for the customization Getting the customization to the user
Set up your GBC build environment Create a customization project Rebuild the GBC
Create a runtime package Deploy on GAS Deploy on JGAS Change the version customization suffix
Manage themes
Add a theme part Add a theme Modify a theme Delete a theme
Replace an image
Change the favicon Change background image for empty tabbed container
Use theme variables
Display or hide the sidebar Customize the chromebar Change checkbox icons Display the Genero context menu Change relog prompt
Use style sheets
Center progress indicator icon Center file loading icon
Use widgets
Add header image Add header image using style class Add header text Add footer text Change file loading icon Redirect application end Extend the MainContainerWidget
Internationalize your app
Add localized text Configure right-to-left languages Customize translation text Default encoding
Migrating customizations
Deploy on JGAS

If you are a J2EE aficionado, you can use the Genero Application Server for Java (JGAS) instead of the Genero Application Server (GAS) to test your customization or bundle it with your application as a J2EE web archive (a.k.a. WAR file).

More details about the JGAS are available in the Genero Application Server for Java User Guide.

Testing your customization using JGAS

If you wish to use the JGAS instead of the GAS to test your customization work, you first need to create a test application bundled in a GAR file. Please read the Genero Business Development Language User Guide to learn how to create a GAR file.

For this example, assume the GAR file is named appName.gar.

Execute the following commands to bundle your application in a WAR file and to execute the WAR file uisng a GBC lookup path pointing to your customization:

$ fglgar war --output <appName>.war --input-gar <appName>.gar
$ fglgar run --war <appName>.war -E res.gbc.lookup.path=<gbc-project-dir>/dist/customization

To test your application with your customized GBC, open the following URL in your preferred browser:

http://localhost:8080/appName/ua/r/appName?gbc=customName

NOTE: When running a standalone JGAS, the default port is 8080. To specify a different port, use the -p flag.

Bundling your custom GBC runtime pcakage in a WAR file.

The fglgar command line allows you to bundle your Genero application as an appName.gar file. For more information regarding the fglgar tool, see the Genero Business Development Language User Guide.

Using the appName.gar, you can execute the following command to create a J2EE web archive named appName.war:

$ fglgar war --output <appName>.war --input-gar <appName>.gar

NOTE: This assumes that the GBC is located in FGLDIR/web_utilities/gbc/gbc. To specify a different location for the GBC, add --gbc gbc-dir.

The resulting J2EE web archive is then deployable on any J2EE server.