Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 62C9510CEF for ; Tue, 7 Jan 2014 19:49:26 +0000 (UTC) Received: (qmail 71248 invoked by uid 500); 7 Jan 2014 19:49:26 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 71156 invoked by uid 500); 7 Jan 2014 19:49:25 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 71141 invoked by uid 99); 7 Jan 2014 19:49:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jan 2014 19:49:24 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of e.semog@gmail.com designates 209.85.216.54 as permitted sender) Received: from [209.85.216.54] (HELO mail-qa0-f54.google.com) (209.85.216.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jan 2014 19:49:19 +0000 Received: by mail-qa0-f54.google.com with SMTP id j7so989073qaq.13 for ; Tue, 07 Jan 2014 11:48:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=YU/8XkzX/Ja3xqXVd0hJXyuNdLO0vc4P0Rdu+T+dm1A=; b=oB54bKts3YaAiOydUirXhpfoIygogt9ksjzojrSzWakJKv8Eoa9pM6+iz+U8a1tdd6 qdkbMdU/g3RF9HatMbpP3icTpnbT4c3lPi370eiypLwfL/fBh8zCaH8a0psF4g9hGOij v0Ht8/pR+qzaEouvpNyQPcZ7w8fY+ezWMTJf+of3cF32/YVetcPSXNXke1XQuuHRtgCI AqYOY+mAgXN3vUiUgZuLadvdqMI/n6jiSbdJJpAC+6YacgR8aa9c5mf7XJ6aZLnJPUm+ HIXJtjwa6V6NBNDFZ6y4HYaWjBCDA3Ec7QDjHEKFyh69QWuKuJxuO6DJYG/YVMFGudEW 11kQ== MIME-Version: 1.0 X-Received: by 10.224.151.145 with SMTP id c17mr193623245qaw.24.1389124138313; Tue, 07 Jan 2014 11:48:58 -0800 (PST) Received: by 10.229.99.133 with HTTP; Tue, 7 Jan 2014 11:48:58 -0800 (PST) In-Reply-To: References: <05AAA2FB-2982-4AA8-8CE2-4AC94DE2C708@gmail.com> Date: Tue, 7 Jan 2014 11:48:58 -0800 Message-ID: Subject: Re: [DISCUSS] Remove the old ActiveMQ Console From: Jim Gomes To: ActiveMQ Dev Content-Type: multipart/alternative; boundary=089e0149cedcd0317504ef66aa7d X-Virus-Checked: Checked by ClamAV on apache.org --089e0149cedcd0317504ef66aa7d Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable +1 the ideas that Claus presented below. I like the idea of a simple drop-in install and a level playing field for replacement consoles. By having a default "headless" install, the security of a production deployment goes way up. On Mon, Jan 6, 2014 at 12:06 AM, Claus Ibsen wrote: > Hi > > I think the old web console should be moved into a sub-project of ActiveM= Q. > Other ASF projects like Felix [1], Karaf [2], etc does this with their > web-consoles. > > That may also make it easier for people to contribute to the > web-console as a sub-project if there codebase is smaller, and not > contains the entire ActiveMQ source code. That may spark a little more > life into the old web-console so people can help maintain it. > > For the standalone ActiveMQ distribution, then installing the old web > console should be an easy step, such as unzipping a .zip file, or > copying a .war / .jar or something to a directory, and allowing to > editing a configuration file to configure the console (port / context > path / or other configurations). Then other 3rd party consoles could > have the *same* installation procedure, so there is even > playing-field. > > For the embedded ActiveMQ distribution for SMX/Karaf users, its > already easy to install the console, as its just like any other > installation using a feature. This is the same for other 3rd party > consoles, and thus there is already an even playing field. > > > > > [1] - > http://felix.apache.org/documentation/subprojects/apache-felix-web-consol= e.html > [2] - http://karaf.apache.org/index/subprojects/webconsole.html > > > On Thu, Jan 2, 2014 at 10:59 AM, Robert Davies > wrote: > > The old/original console is no longer fit for purpose, it is hard to > maintain, the source of a lot of security issues [1] over the last few > years. > > > > There is another thread about using hawtio as the console going forward= , > and without going into all the gory details it is probably likely that > there may be no web console shipped at all in future releases of ActiveMQ= . > The JMX naming hierarchy was improved for ActiveMQ 5.8, such that its eas= y > to view the running status of an ActiveMQ broker from 3rd party tools suc= h > as jconsole, visualvm or hawtio. Regardless of the outcome of the other > discussion [2] - It doesn=92t help the ActiveMQ project to try and mainta= in a > static web console any more. > > > > I propose we remove the old web console from the ActiveMQ 5.10 release = - > thoughts ? > > > > > > > > [1] > https://issues.apache.org/jira/browse/AMQ-2714?jql=3Dproject%20%3D%20AMQ%= 20AND%20text%20~%20%22XSS%22 > > [2] > http://activemq.2283324.n4.nabble.com/Default-Web-Console-td4675705.html > > > > Rob Davies > > =97=97=97=97=97=97=97=97 > > Red Hat, Inc > > http://hawt.io - #dontcha > > Twitter: rajdavies > > Blog: http://rajdavies.blogspot.com > > ActiveMQ in Action: http://www.manning.com/snyder/ > > > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: cibsen@redhat.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > Make your Camel applications look hawt, try: http://hawt.io > --089e0149cedcd0317504ef66aa7d--