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 Mon, 01 Dec 2014 06:19:13 GMT

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

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

Been hacking on this some more. I was able to lift the resources and annotated classes from
previously into a version that works with Jersey, Jackson and Grizzly

https://github.com/joshelser/accumulo/tree/jersey-monitor

Need to address some minor semantic issues in the resources, but that won't be too bad. I
need to start looking how to replace the HTML renderings which is the big unknown presently.
Looking at https://jersey.java.net/documentation/latest/mvc.html, but I need to figure out
what sounds the best. Would using the "standard" JSP be easiest?

Switching over from embedded Jetty to Grizzly has been nice, but I'm not sure of the technical
reasons for choosing one over the other. I mainly used Grizzly because it worked and I had
some examples I could leverage from Jersey. Any info would be appreciated.

> 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