JAR File's config.xml"
From Documentation
m |
|||
| Line 1: | Line 1: | ||
{{ZKConfigurationReferencePageHeader}} | {{ZKConfigurationReferencePageHeader}} | ||
| + | |||
| + | A JAR file could contain a configuration file that will override the default configuration of a ZK application. The file must be named as <tt>config.xml</tt> and placed under the <tt>/metainfo/zk</tt> directory. Of course, the configuration specified in <tt>WEB-INF/zk.xml</tt> has higher priority. It will override the configuration specified in <tt>/metainfo/zk/config.xml</tt>. | ||
| + | |||
| + | By use of <tt>config.xml</tt>, a JAR file could change the default configuration without user's notice, such as adding a desktop listener, setting a library property, and so on. For more information, please refer to [[ZK Developer's Reference/Customization/Packing Code|ZK Developer's Reference: Packing Code]]. | ||
{{ZKConfigurationReferenceHeadingToc}} | {{ZKConfigurationReferenceHeadingToc}} | ||
{{ZKConfigurationReferencePageFooter}} | {{ZKConfigurationReferencePageFooter}} | ||
Revision as of 06:51, 21 December 2010
A JAR file could contain a configuration file that will override the default configuration of a ZK application. The file must be named as config.xml and placed under the /metainfo/zk directory. Of course, the configuration specified in WEB-INF/zk.xml has higher priority. It will override the configuration specified in /metainfo/zk/config.xml.
By use of config.xml, a JAR file could change the default configuration without user's notice, such as adding a desktop listener, setting a library property, and so on. For more information, please refer to ZK Developer's Reference: Packing Code.