Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 48295 invoked from network); 22 Aug 2008 16:17:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Aug 2008 16:17:43 -0000 Received: (qmail 85315 invoked by uid 500); 22 Aug 2008 16:17:35 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 85270 invoked by uid 500); 22 Aug 2008 16:17:34 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 84832 invoked by uid 99); 22 Aug 2008 16:17:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2008 09:17:33 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2008 16:16:45 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 90077234C1C6 for ; Fri, 22 Aug 2008 09:16:44 -0700 (PDT) Message-ID: <1865983192.1219421804588.JavaMail.jira@brutus> Date: Fri, 22 Aug 2008 09:16:44 -0700 (PDT) From: "Chris Rose (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Commented: (AXIS2-943) Add support for disengagement of modules to administration web frontend In-Reply-To: <30511988.1154323994069.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AXIS2-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624890#action_12624890 ] Chris Rose commented on AXIS2-943: ---------------------------------- I don't see any evidence that this capability is actually present in the web administration interface, and it's really a very useful one to have. Can someone please confirm if this issue is actually fixed, and if so please document how to perform the desired operation? Specifically, I would like to see the following: Globally disengage a module Disengage a module that was engaged at the service, service group, or operation level at that same level (ie: if I turned on a module for a service, allow me to turn it off for that selfsame service) This applies in this case to Axis2 1.3. > Add support for disengagement of modules to administration web frontend > ----------------------------------------------------------------------- > > Key: AXIS2-943 > URL: https://issues.apache.org/jira/browse/AXIS2-943 > Project: Axis 2.0 (Axis2) > Issue Type: New Feature > Components: kernel > Affects Versions: 1.0 > Reporter: Thilo Frotscher > Assignee: Deepal Jayasinghe > > It would be great if modules could be disengaged using the admin frontend! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org