JAR File's config.xml"
From Documentation
m (correct highlight (via JWB)) |
|||
| 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 < | + | A JAR file could contain a configuration file that will override the default configuration of a ZK application. The file must be named as <code>config.xml</code> and placed under the <code>/metainfo/zk</code> directory. Of course, the configuration specified in <code>WEB-INF/zk.xml</code> has higher priority. It will override the configuration specified in <code>/metainfo/zk/config.xml</code>. |
| − | By use of < | + | By use of <code>config.xml</code>, a JAR file could change the default configuration without a 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 08:51, 19 January 2022
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 a 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.