accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3005) Convert the monitor into a real REST server
Date Tue, 02 Dec 2014 21:26:13 GMT

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

Josh Elser commented on ACCUMULO-3005:
--------------------------------------

bq. are there specific advantages you've encountered that make the switch compelling?

In using JaxRS resources over Servlets, there is definitely much more literature on configuring
Grizzly with said resources, which is primarily how my decision was made so far. I haven't
actually been able to find a technical difference (or even a comparison) between the two as
to why you'd choose Jetty over Grizzly or vice versa (oddly..). I also haven't found any docs
on how to configure Jetty to do the jaxrs stuff (as opposed to servlets) either.

I did find that Grizzly publishes a WADL automagically which was pretty cool for me to at
least validate that my resources were being loaded. I could see some benefit from that for
consumers as well, but that's by no means a strong differentiation.

> Convert the monitor into a real REST server
> -------------------------------------------
>
>                 Key: ACCUMULO-3005
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3005
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: monitor
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>         Attachments: 0001-ACCUMULO-3005-Initial-round-of-changes-for-a-proper-.patch
>
>
> The monitor works well for what it does, but it's very much so cobbled together. HTML
is hand generated. Static state is used liberally which makes testing near impossible. View
and controller logic are tightly intertwined which also adds to the testability problem.
> I've been working on porting the functionality from the existing monitor to a proper
rest service using [dropwizard|https://dropwizard.github.io/dropwizard/]. It's not completely
functional yet, but it has a number of improvements of the existing monitor code.
> I thought I would post what I have already and let people give some feedback if they're
interested. Help is always welcome. https://github.com/joshelser/accumulo/tree/dropwizard.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message