You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/10/17 08:35:50 UTC
[jira] Closed: (SLING-58) Add support for templated JavaScript
[ https://issues.apache.org/jira/browse/SLING-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-58.
----------------------------------
Resolution: Fixed
Support has been added and this can now be closed.
> Add support for templated JavaScript
> ------------------------------------
>
> Key: SLING-58
> URL: https://issues.apache.org/jira/browse/SLING-58
> Project: Sling
> Issue Type: Improvement
> Components: microsling
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> We have a simple FilterReader class lying around which supports simple templated JavaScript along similar to JSP. The reader filters the templated java script and converts it to standard java script as follows:
> * a 1:1 mapping of lines from templated to standard java script is preserved
> * <%-- ... --> are not transferred to standard java script
> * template text is enclosed in "out.write()" method calls
> * <% ... %> encloses java script code used as is
> * <%= ... %> encloses a java script expression eclosed in an out.write() call
> * HTML comments <!-- ... --> are handled just as any template code
> Lets call the templated JavaScript "ECMA Server Pages" and let them have script file extensions of ".esp" and add support to the RhinoJavascriptServlet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.