org.zkoss.zk.config.path"
From Documentation
m |
|||
| Line 7: | Line 7: | ||
[since 5.0.7] | [since 5.0.7] | ||
| − | It specifies the second configuration file in addition to <tt>WEB-INF/zk.xml</tt>. | + | It specifies the second configuration file in addition to <tt>WEB-INF/zk.xml</tt>. This is useful if you have two or more environments, such as testing and production. Then, you could put the different configuration into separated files and load the required files based on the requirement. |
The value could be one of the following: | The value could be one of the following: | ||
Revision as of 08:17, 5 August 2011
Property:
org.zkoss.zk.config.path
Default: none [since 5.0.7]
It specifies the second configuration file in addition to WEB-INF/zk.xml. This is useful if you have two or more environments, such as testing and production. Then, you could put the different configuration into separated files and load the required files based on the requirement.
The value could be one of the following:
- A servlet path, such as
/WEB-INF/config/zk-extra.xml - A file path, such as
file:///home/http/zk.xmlandfile:///C:/test/zk.xml, if Windows. Notice it must start withfile://[1]. - A URL, such as
http://foo.com/config/zk.xml. Notice it must starts withhttp://,https://, andftp://.
For example, assume you put the configuration in a file called /configs/zk-production.xml, then you could specify -Dorg.zkoss.zk.config.path=file:/configs/zk-production.xml as one of the arguments when starting the Web server.
Version History
| Version | Date | Content |
|---|---|---|
| 5.0.7 | April, 2011 | Introduced |
- ↑ For more information about the URI of a file, please refer to File URI scheme.