You can configure property filtering templates that will be applied when REST requests invoke them. Configure filtering templates for specific Nucleus components, repositories, or Java classes in the /atg/rest/filtering/filteringConfiguration.xml file, just as you would for default filtering. See Default Filtering in Legacy REST.

Include a template element in the rest-filtering element for each template you want to configure. Add an id attribute to the template element. REST clients will refer to this id value when invoking the template. Configure the filtering behavior of the template using the same elements and syntax that you would in a component element for default filtering. See Default Filtering in Legacy REST.

The following filteringConfiguration.xml file defines a filtering template.

  <template id="myfiltertemplate" name="/atg/MyDog" default-include="true">
    <property name="tricks" hidden="true" />

Invoke filtering templates with the atg-rest-property-filter-templates control parameter. Include the id of a template or a JSON array of ids as the value of this parameter.

The following REST request invokes the filtering template configured in the example above.

curl -v -b cookies.txt -X GET \http://myserver:7003/rest/bean/atg/

The following REST request invokes multiple filtering templates.

curl -v -b cookies.txt -X GET \http://myserver:7003/rest/bean/atg/MyDog?

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