Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 23526 invoked from network); 27 Jul 2007 01:45:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jul 2007 01:45:27 -0000 Received: (qmail 68669 invoked by uid 500); 27 Jul 2007 01:45:25 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 68609 invoked by uid 500); 27 Jul 2007 01:45:25 -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 68597 invoked by uid 99); 27 Jul 2007 01:45:25 -0000 Received: from Unknown (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jul 2007 18:45:25 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED 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; Fri, 27 Jul 2007 01:45:23 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9375B7141F2 for ; Thu, 26 Jul 2007 18:45:03 -0700 (PDT) Message-ID: <7664072.1185500703577.JavaMail.jira@brutus> Date: Thu, 26 Jul 2007 18:45:03 -0700 (PDT) From: "Mark Badorrek (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Created: (AXIS2-3026) New AxisConfigurator that operates within the aar file MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org New AxisConfigurator that operates within the aar file ------------------------------------------------------ Key: AXIS2-3026 URL: https://issues.apache.org/jira/browse/AXIS2-3026 Project: Axis 2.0 (Axis2) Issue Type: Wish Components: kernel Affects Versions: nightly Environment: Not specific Reporter: Mark Badorrek Fix For: nightly Currently there are several AxisConfigurators: FileSystemConfigurator URLBasedAxisConfigurator etc I feel that we also need an AxisConfigurator that can read an axis_client.xml file and client repository that are stored in the aar file. This would allow an axis service to make client-calls to other axis services using different configurations from the parent configuration. For example: I have an axis service 'foo' that is a plain old websevice - nothing special. Now consider that it has been invoked by a client. 'foo' must now make a couple of webservice calls of its own, but this time it will (for example) engage 'rampart' and disengage'addressing' for both of its client calls. As such each configuration will have its own rampart callback classes etc. Currently there is no way to include the required 'client1_axis2.xml', client1_repository', 'client2_axis2.xml', client2_repository', within the aar file and have them loaded. I'd like to see an 'ServiceClassloaderAxisConfigurator' to allow these artifacts to be stored within the aar file so that the entire 'foo' webservice is a single file deploy. The 'client1_AxisConfiguration' and 'client1_AxisConfiguration' should also be cached as there is a high probability that they will be required agin and again. -- 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