[jira] [Commented] (HBASE-3835) Switch web pages to Jamon template engine instead of JSP

["stack (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489597#comment-13489597 ] 

stack commented on HBASE-3835:
------------------------------

[~vanto] I added a mention to our NOTICE.txt file that jamon the template engine is MPL (See HBASE-7087).  Thanks.
                
> Switch web pages to Jamon template engine instead of JSP
> --------------------------------------------------------
>
>                 Key: HBASE-3835
>                 URL: https://issues.apache.org/jira/browse/HBASE-3835
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 0.92.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.92.0
>
>         Attachments: hbase-3835.txt, hbase-3835.txt, hbase-3835.txt
>
>
> Jamon (http://jamon.org) is a template engine that I think is preferable to JSP. You can read an interview with some comparisons vs JSP here: http://www.artima.com/lejava/articles/jamon.html
> In particular, I think it will give us the following advantages:
> - Since we'll have a servlet in front of each template, it will encourage us to write less inline Java code and do more code in the servlets.
> - Makes proper unit testing easier since you can trivially render a template and pass in mock arguments without having to start a whole HTTP stack
> - Static typing of template arguments makes it easier to know at compile-time if you've made a mistake.
> Thoughts? I converted the Master UI yesterday and only took a couple hours.

--
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