[ https://issues.apache.org/jira/browse/SLING-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Klco resolved SLING-2834. ----------------------------- Resolution: Fixed Added the new variables and support for saving included content into the sling:include tag > sling:include support two new attributes > ---------------------------------------- > > Key: SLING-2834 > URL: https://issues.apache.org/jira/browse/SLING-2834 > Project: Sling > Issue Type: Improvement > Components: Servlets > Affects Versions: Scripting JSP-Taglib 2.1.8 > Reporter: Michael J. Kelleher > Assignee: Dan Klco > Priority: Minor > Labels: features > Original Estimate: 72h > Remaining Estimate: 72h > > Look at the functionality of c:import for context to this request: > http://docs.oracle.com/cd/E17802_01/products/products/jsp/jstl/1.1/docs/tlddocs/index.html > That tag supports 2 attributes: var and varReader. These two variable > prevent the included resource from automatically being including the output > of current requests 'out' Stream. They do the following: > var - stores the output of the included resource as a String in the scoped > variable identified by 'var'. > varReader - stores a Reader to the included content in the scoped variable > 'varReader'. > Both of these would likely need the 'scope' attribute as well. > The current use case I have for this is that I do not want to extend or > modify the functionality of the included resource to serve my new > requirement. The change I need to make to the markup is fairly small, and > would not want to have to maintain a new component for such a small change. > I want to include a transformed version of the included resource. The > addition of these two attributes would allow me to store the resultant markup > and transform it before including it within my current request. > I can certainly write this functionality myself (and will be using > sling:include) but it would be nice if sling:include itself supported this > functionality. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira