Deploying Jasper web applications
- A more or less precise definition of pseudo-code
- Concrete language equivalents for pseudo-code functions
- Securing Jasper web applications
- Fixing broken logging
- A complete TemplateForm class
- More on form validation and styles
- Handling forms with tri-state return values
- The indispensible TemplateSQL class
- Deploying Jasper web applications
Configuring a Jasper web application to sit within a different context should require no more than amendments to the 'global.config' configuration file. The following listing shows an imaginary global configuration file for this web application.
#xSuppressSQLLogging=TRUE gFormMethod=GET LOCAL appPath=/jasper.sourceforge.net/ rootDir=D:\Sites\jasper.sourceforge.net\ dbHost=localhost dbUser=... dbPassword=... dbName=jasper #REMOTE #appPath=/ #rootDir=... #dbHost=... #dbUser=... #dbPassword=... #dbName=...
Here both the local and remote settings are present. The conventional 'appPath' and 'rootDir' variables are included, for example, together with the database related configuration. The local settings are the only ones that are currently active, however, with the remote settings commented out.
Just prior to deployment, the situation can be revsersed with the local settings being commented out and the comments before the remote settings being removed. Note that no comment is needed in front of the 'LOCAL' heading. There is no equals character '=' on this line, so it is effectively just ignored.
Last updated: Thursday, 16th December 2010, 05:10 PM
User comments:
There are none.