Tag: pageLayoutCache
The wcpgl:pageLayoutCache tag allows page layout JSP files
to dynamically generate and set dependency IDs. These IDs can be used so that a layout JSP file can
be invalidated when the page layout assignment for the layout JSP file
changes.
For more information about Commerce Composer caching, see Commerce Composer layout caching and invalidation.
Tag information | |
---|---|
Body Content | empty |
Name | Required | Request-time | Type | Description |
---|---|---|---|---|
pageDesignData |
false |
true |
java.lang.String |
The Page Design Type SDO object that returns from a service call to Get PageDesign. |
pageLayoutId |
false |
true |
java.lang.String |
If the value for this attribute is set, use this layout ID when you create the dependency rules. If the value is not set, the layout ID is retrieved from the pageDesignData object set. If pageDesignData object is also not set, then no dependency rules are set. |
pageId |
false |
true |
java.lang.String |
If the value for this attribute is set, use the page ID when you create the dependency rules. This value is expected to be set for content pages that have a dependency on the PLPAGE database table. |
EXAMPLE
If you want a JSP to generate a dependency ID for triggering a cache invalidation, you must include the tag within the JSP file in the following format:<wcpgl:pageLayoutCache pageLayoutId="${pageDesign.layoutID}"/>
A single dependency ID is generated from a tag within the layout JSP. If the associated layout itself is modified by the business user, then this dependency ID triggers a cache invalidation.