Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 95671 invoked from network); 17 Nov 2006 06:08:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Nov 2006 06:08:00 -0000 Received: (qmail 93156 invoked by uid 500); 17 Nov 2006 06:08:10 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 92560 invoked by uid 500); 17 Nov 2006 06:08:09 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 92532 invoked by uid 99); 17 Nov 2006 06:08:09 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Nov 2006 22:08:09 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Nov 2006 22:07:58 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id AB752714322 for ; Thu, 16 Nov 2006 22:07:37 -0800 (PST) Message-ID: <10559521.1163743657684.JavaMail.jira@brutus> Date: Thu, 16 Nov 2006 22:07:37 -0800 (PST) From: "Matt Hogstrom (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Updated: (GERONIMO-1511) Rewrite JMS portlet In-Reply-To: <960478755.1137735401969.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/GERONIMO-1511?page=all ] Matt Hogstrom updated GERONIMO-1511: ------------------------------------ Fix Version/s: Wish List (was: 1.2) > Rewrite JMS portlet > ------------------- > > Key: GERONIMO-1511 > URL: http://issues.apache.org/jira/browse/GERONIMO-1511 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: ActiveMQ, connector, console > Affects Versions: 1.0 > Reporter: Aaron Mulder > Fix For: Wish List > > > The JMS connection factory and destination portlets should be replaced by a single JMS manager portlet. This should use the JMSManager and show all the available JMS brokers, listing the available connection factories and destinations for each one. When adding a connection factory or destination, it should use the JSR-88 DConfigBeans to construct the deployment plan for the new configuration. I'm not yet sure whether it should group the resources by configuration, perhaps just list the owning configuration there. I'm also not sure whether it's important to be able to add connection factories and destinations simultaneously in a single new configuration -- probably not, though it would be nice in terms of generating plans and so on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira