zk.xml"
Tmillsclare (talk | contribs) m |
|||
| Line 18: | Line 18: | ||
For library providers, <code>zk.xml</code> is better to be packed with a JAR file. It can be done by placing zk.xml in the <code>metainfo/zk</code> directory identifiable by classpath (i.e., in a JAR file). | For library providers, <code>zk.xml</code> is better to be packed with a JAR file. It can be done by placing zk.xml in the <code>metainfo/zk</code> directory identifiable by classpath (i.e., in a JAR file). | ||
| − | Notice that <code>zk.xml</code> found in the classpath is parsed first. It means <code>WEB-INF/zk.xml</code> has higher priority. | + | Notice that <code>zk.xml</code> found in the classpath is parsed first. It means <code>WEB-INF/zk.xml</code> has higher priority (since it overrides <code>metainfo/zk/zk.xml</code> if conflicts). |
{{ZKConfigurationReferenceHeadingToc}} | {{ZKConfigurationReferenceHeadingToc}} | ||
Revision as of 06:24, 14 July 2010
WEB-INF/zk.xml is the configuration descriptor of ZK. This file optional. If you need to configure ZK differently from the default, you could provide a file called zk.xml under the WEB-INF directory.
The root element must be <zk>. Then, you could specify any combination of the following element under the root element.
File Location
You can place zk.xml in either a WAR file or a JAR file.
WEB-INF/zk.xml
zk.xml is usually packed with a Web application and it shall be located under WEB-INF.
metainfo/zk/zk.xml
[since 3.6.0]
For library providers, zk.xml is better to be packed with a JAR file. It can be done by placing zk.xml in the metainfo/zk directory identifiable by classpath (i.e., in a JAR file).
Notice that zk.xml found in the classpath is parsed first. It means WEB-INF/zk.xml has higher priority (since it overrides metainfo/zk/zk.xml if conflicts).