[
https://issues.apache.org/jira/browse/HBASE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399636#comment-13399636
]
Elliott Clark commented on HBASE-6259:
--------------------------------------
Sure.
I'm not really advocating for jsp. I'm pretty much advocating the same thing
that was advocated in HBASE-3835. Our pages have very bad separation between
the html view and domain models. Things like per-region metrics, and getting
config values use java code embedded in html way too much. Jamon seems like it
has not seen the adoption of some other solutions and it hasn't really followed
the trend of moving computation out of the template; in fact it looks like
there has been no work on jamon in a while. In addition template inheritance is
pretty messy in jamon, and now that we have more of a ui template it would be
nice to use that so that changes like the HBASE-6219 could be done in one place.
I don't have strong opinions on specific templating languages, however I do
think picking one that minimizes java code would be good.
> Unify all of the templates into one templating language
> -------------------------------------------------------
>
> Key: HBASE-6259
> URL: https://issues.apache.org/jira/browse/HBASE-6259
> Project: HBase
> Issue Type: Improvement
> Components: master, regionserver
> Affects Versions: 0.96.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Labels: noob
>
> Right now .jsp and jammon templates can't share common parts as they are
> un-related. We should move to one templating language. Maybe also move away
> from jamon.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
