Difference between revisions of "Xebra Webapp Config File"
(→Example) |
(→host) |
||
Line 19: | Line 19: | ||
*Description: Defines the port where the webapp is listening to server request. Use a different port for every webapp | *Description: Defines the port where the webapp is listening to server request. Use a different port for every webapp | ||
− | == | + | ==server_host== |
*Type: STRING | *Type: STRING | ||
− | *Description: | + | *Description: Specifies the host of the xebra server |
==taglibs== | ==taglibs== |
Revision as of 12:14, 20 August 2009
About | Installation | Documentation | Tutorials | Frequently Asked Questions
Whenever the server (re)loads its config file, the webapp_root folder is scanned for webapp 'config.wapp' files. These files represent the webapps that are loaded into the server. The webapp config files are formated in Java Script Object Notation (JSON).
Contents
Properties
ecf
- Type: Path to file
- Description: Specifies the path to the webapp's ecf file.
name
- Type: STRING
- Description: The name of the webapp
port
- Type: NATURAL
- Description: Defines the port where the webapp is listening to server request. Use a different port for every webapp
server_host
- Type: STRING
- Description: Specifies the host of the xebra server
taglibs
- Type: ARRAY
- Description: Use this property to tell the translator which tag-libraries are used by this webapplication.
name
- Type: STRING
- Description: The name of the taglib
ecf
- Type: STRING
- Description: Specifies the name of the taglib's ecf file
path
- Type: Path to dir
- Description: Specifies the dir to the taglib
Example
{ "ecf": "$XEBRA_DEV/www/servercontrol/servercontrol.ecf", "name": "servercontrol", "port": "55003", "server_host": "localhost", "taglibs": [ { "name": "xebra_taglibrary_base", "ecf": "xebra_taglibrary_base.ecf", "path": "$XEBRA_LIBRARY/xebra_taglibrary_base" }, { "name": "xebra_taglibrary_form", "ecf": "xebra_taglibrary_form.ecf", "path": "$XEBRA_LIBRARY/xebra_taglibrary_form" } ] }