accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3005) Convert the monitor into a real REST server
Date Wed, 03 Dec 2014 01:41:13 GMT


Josh Elser commented on ACCUMULO-3005:

Understood. Right now, I'm aiming to keep a single module for the "API" and then let that
be runnable via *some* embedded server (jetty or grizzly). I'd like to get a separate module
for a generic WAR, but I'm guessing my motivation to test it for "generalness" will run out
after the 2nd container/app-server.

It would be nice to at least support (non-embedded) Jetty and Tomcat for a first pass, I think.
I agree with you -- let's take a step back once things are solidified and we can decide the
path we want to take after. Feel free to look at the diff on my github if you're curious.
After I get it converted over to an Application, I'll try to put up a proper patch.

> Convert the monitor into a real REST server
> -------------------------------------------
>                 Key: ACCUMULO-3005
>                 URL:
>             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|]. 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.

This message was sent by Atlassian JIRA

View raw message