[
https://issues.apache.org/jira/browse/HBASE-20617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491117#comment-16491117
]
Mike Drob commented on HBASE-20617:
-----------------------------------
statically compiled jsp allows us to catch some errors at compile time, like if
a field or method is renamed and used by the jsp, then that surfaces during
build time instead of throwing lots of inscrutable errors the next time
somebody happens to look at the web ui (could be days or weeks later).
I am sympathetic to the idea of enabling hot fixes, so maybe there is a
possible hybrid approach we can do? Where we still static compile, but then
allow for raw jsp in the web container? I'm not up to date on the state of the
art for front-end work, but I imagine there have been improvements to tools
since we initially set up the jsp stuff in ~2014.
> Upgrade/remove jetty-jsp
> ------------------------
>
> Key: HBASE-20617
> URL: https://issues.apache.org/jira/browse/HBASE-20617
> Project: HBase
> Issue Type: Improvement
> Reporter: Sakthi
> Priority: Minor
>
> jetty-jsp removed after jetty-9.2.x version. We use the 9.2 version. Research
> so far brings out that apache-jsp might be of interest to us in jetty-9.4.x
> version(as JettyJspServlet.class is in apache-jsp). Yet to figure out about
> jetty-9.3.x.
> Filing to track this along.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
