Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 39949 invoked from network); 30 Nov 2006 04:48:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Nov 2006 04:48:43 -0000 Received: (qmail 99879 invoked by uid 500); 30 Nov 2006 04:48:52 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 99864 invoked by uid 500); 30 Nov 2006 04:48:52 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 99853 invoked by uid 99); 30 Nov 2006 04:48:51 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Nov 2006 20:48:51 -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; Wed, 29 Nov 2006 20:48:42 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id AA03B7142EC for ; Wed, 29 Nov 2006 20:48:21 -0800 (PST) Message-ID: <27419998.1164862101671.JavaMail.jira@brutus> Date: Wed, 29 Nov 2006 20:48:21 -0800 (PST) From: "Damitha Kumarage (JIRA)" To: axis-c-dev@ws.apache.org Subject: [jira] Commented: (AXIS2C-427) There should be a way of specifying sperate axis2.xml files for client and server. In-Reply-To: <28883246.1164400081998.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 [ http://issues.apache.org/jira/browse/AXIS2C-427?page=comments#action_12454532 ] Damitha Kumarage commented on AXIS2C-427: ----------------------------------------- in dep_engine_load_client we can load a axis2_client.xml. I think implementing this is simple. But even if we do this how can we dirrerentiate server and client modules? There could be other complications arising by trying to do this. So the simple thing is having two repositories for client and server which will let us have the code simple > There should be a way of specifying sperate axis2.xml files for client and server. > ---------------------------------------------------------------------------------- > > Key: AXIS2C-427 > URL: http://issues.apache.org/jira/browse/AXIS2C-427 > Project: Axis2-C > Issue Type: Improvement > Components: core/deployment > Affects Versions: Current (Nightly) > Reporter: Dinesh Premalal > Priority: Minor > Fix For: 0.96 > > > Now both client and server share the axis2.xml file in the repository. If one need to have differant configuration for client and server, then need to maintain two repositories. I think it's better if we could provide a way of specifing differant axis2.xml for client and server, while using same repository. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-c-dev-help@ws.apache.org