Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 96EF110E8F for ; Wed, 3 Dec 2014 01:41:13 +0000 (UTC) Received: (qmail 63555 invoked by uid 500); 3 Dec 2014 01:41:13 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 63499 invoked by uid 500); 3 Dec 2014 01:41:13 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 63093 invoked by uid 99); 3 Dec 2014 01:41:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Dec 2014 01:41:13 +0000 Date: Wed, 3 Dec 2014 01:41:13 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3005) Convert the monitor into a real REST server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232444#comment-14232444 ] 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: 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)