Static Export
(Difference between revisions)
(added intro for Static export) |
|||
| Line 3: | Line 3: | ||
OpenCms is not only able to export static files like images from its [[Virtual File System]] - it can also export the a complete page, after it has been processed by a [[JSP Template]]. Of course this makes only sense for resources, that do not have to change with each request. Because of this, Static Export can be switched on or off for each individual resource. | OpenCms is not only able to export static files like images from its [[Virtual File System]] - it can also export the a complete page, after it has been processed by a [[JSP Template]]. Of course this makes only sense for resources, that do not have to change with each request. Because of this, Static Export can be switched on or off for each individual resource. | ||
| − | See also: [[Static Export After Publish]], [[Static Export On Demand]] and [[ | + | See also: [[Static Export After Publish]], [[Static Export On Demand]] and [[Static Export configuration]]. |
Revision as of 13:12, 8 November 2006
OpenCms is capable of exporting Resources into the Real File System. These files can then be served by a normal web server, without involving any more processing on the side of OpenCms. This is mainly used to increase performance and is called Static Export.
OpenCms is not only able to export static files like images from its Virtual File System - it can also export the a complete page, after it has been processed by a JSP Template. Of course this makes only sense for resources, that do not have to change with each request. Because of this, Static Export can be switched on or off for each individual resource.
See also: Static Export After Publish, Static Export On Demand and Static Export configuration.
