Calculating the Content Path from the Page Request URL

Note: The information in this section applies to page requests processed by the AssemblerPipelineServlet only. For information about page requests that are processed using the InvokeAssembler servlet bean, see the InvokeAssembler section.

For page requests processed by the AssemblerPipelineServlet, the AssemblerTools.getContentPath() method calculates the content path to pass to the Assembler (for example, /browse). The content path identifies the page in Experience Manager whose content should be rendered. The content path is relative to the current site; for example, if the current site is storeus and the content path is /browse, then the /browse page will be retrieved for the storeus site.

The getContentPath() method extracts the content path from the request URL by removing substrings that match the values of properties of the siteConfiguration item for the site. For example, if a request is made to http://localhost:8080/crs/storeus/browse/:

  1. The getContentPath() method gets the request URI using the atg.servlet.ServletUtil class. In this case, the request URI is:

    /crs/storeus/browse/

  2. If the AssemblerTools.removeSiteBaseURL property is true, getContentPath() compares the request URI with the site base URL (the value of the siteConfiguration item’s productionURL property). If the AssemblerTools.includeAdditionalProductionURLs property is also true, the getContentPath() method compares the request URI with the values of the siteConfiguration item’s additionalProductionURLs property, as well as with the value of productionURL. If one of the URLs matches a substring of the request URI, getContentPath() removes that substring from the request URI.

  3. If the AssemblerTools.removeContextRoot property is true and the site base URL has not been removed, getContentPath() compares the request URI with the context root (the value of the siteConfiguration item’s contextRoot property). If there is a match, getContentPath() removes the context root from the request URI.

So, in this example, if one of the production URLs is /crs/storeus, the resulting content path is /browse/. If none of the URLs match the request URI and the context root is /crs, the resulting content path is /storeus/browse/.

Copyright © 1997, 2017 Oracle and/or its affiliates. All rights reserved. Legal Notices