The ContentRequestUrlDroplet
, which extends the FrameworkUrlDroplet
, generates a URL with the content URI or content collection name encoded as a URL parameter. The droplet generates URLs for category browse navigation links, default and follow-on content URIs, as well as the auto suggest collection content.
Class |
|
---|---|
Components |
|
The servlet bean identifies the default URL for the search results page using the searchResultsPageURL
property. By default, the value is set to /framework.jsp?ps=cmcCatalogPS&
. The
p=cmcProductCatalogSearchContentRequestUrlDroplet
contains the following parameters. Note that only a single dimensionId
, contentPath
or navigationAction
parameter can be used to determine the content URI. If no value is provided for contentPath
or navigationAction
, the default content URI will be used:
Input Parameters
url
– Optional. The base URL on which theContentURI
parameter will be encoded. If this parameter is not provided, the value will default to the configuredsearchResultsPageURL
dimensionId
– Optional. This identifies the dimension ID. When an value is specified, the default content URI is used with a navigation filter parameter (N=x) to specify the dimension valuecontentPath
– Optional. This parameter specifies a value to use as the content URI in the resulting URLnavigationAction
– Optional. An EndecaNavigationAction
object from which to construct the content URIrecordOffset
– Optional. The result record offset for paging. When a value is provided, thenavigationAction
should be a paging template where record offset can be substituted into the URIrecordsPerPage
– Optional. Specifies the number of records per page for the results. When a value is provided, thenavigationAction
should be a paging template where records per page can be substituted into the URI
Open Parameters
output
– This parameter is rendered only once.
Examples
The following example identifies the defaultContentURI
as the content path:
<dsp:droplet name="ContentRequestURLDroplet"> <dsp:param name="contentPath" value="${endecaConfig.defaultContentURI}" /> <dsp:oparam name="output"> <dsp:getvalueof var="contentURL" bean="ContentRequestURLDroplet.url" /> </dsp:oparam> </dsp:droplet>
The following example uses a navigationAction
:
<dsp:droplet name="ContentRequestUrlDroplet"> <dsp:param name="navigationAction" value="${sortOption}" /> <dsp:oparam name="output"> <dsp:getvalueof var="contentURL" bean="ContentRequestURLDroplet.url" /> </dsp:oparam> </dsp:droplet>
The following is an example of a navigation action with a record offset:
<dsp:droplet name="ContentRequestURLDroplet"> <dsp:param name="navigationAction" value="${resultsListContentItem['pagingActionTemplate']}"/> <dsp:param name="recordOffset" value="${pageRecordIndex}"/> <dsp:param name="recordsPerPage" value="${recsPerPage}"/> <dsp:oparam name="output"> <dsp:getvalueof var="contentURL" bean="ContentRequestURLDroplet.url"/> <a href="#" onclick="atgSubmitAction({url: '${contentURL}'});return false;"> <c:out value="${pageNumber}"/></a> </dsp:oparam> </dsp:droplet>