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 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.