The extendlet-check-period Element"
From Documentation
m |
m (correct highlight (via JWB)) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 6: | Line 6: | ||
[Default: -1 (never expired)] | [Default: -1 (never expired)] | ||
| − | It specifies the time, in seconds, to wait before checking whether a resource loaded by an extendlet is modified. An extendlet is a processor to load the resources usually located in classpath, such as < | + | It specifies the time, in seconds, to wait before checking whether a resource loaded by an extendlet is modified. An extendlet is a processor to load the resources which are usually located in classpath, such as <code>~./zul/desktop.dsp</code>. |
| − | Resources located in classpath are usually packed as a JAR file, so they are immutable and not need to check if modified. However, in a development environment, you might want to check if they are deployed without reloading the JAR files. | + | Resources located in classpath are usually packed as a JAR file, so they are immutable and not need to check if modified. However, in a development environment, you might still want to check out if they are deployed without reloading the JAR files. |
=Version History= | =Version History= | ||
Latest revision as of 10:19, 19 January 2022
Syntax:
<extendlet-check-period>a_number</extendlet-check-period>
[Default: -1 (never expired)]
It specifies the time, in seconds, to wait before checking whether a resource loaded by an extendlet is modified. An extendlet is a processor to load the resources which are usually located in classpath, such as ~./zul/desktop.dsp.
Resources located in classpath are usually packed as a JAR file, so they are immutable and not need to check if modified. However, in a development environment, you might still want to check out if they are deployed without reloading the JAR files.
Version History
| Version | Date | Content |
|---|---|---|