Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 605 invoked from network); 29 Mar 2005 13:42:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Mar 2005 13:42:13 -0000 Received: (qmail 80732 invoked by uid 500); 29 Mar 2005 13:42:13 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 80626 invoked by uid 500); 29 Mar 2005 13:42:13 -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 80613 invoked by uid 99); 29 Mar 2005 13:42:13 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_40_50,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from mtagate2.uk.ibm.com (HELO mtagate2.uk.ibm.com) (195.212.29.135) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 29 Mar 2005 05:42:11 -0800 Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate2.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j2TDg8pW302664 for ; Tue, 29 Mar 2005 13:42:08 GMT Received: from d06av04.portsmouth.uk.ibm.com (d06av04.portsmouth.uk.ibm.com [9.149.37.216]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j2TDg77Q161180 for ; Tue, 29 Mar 2005 14:42:08 +0100 Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j2TDg7C9019094 for ; Tue, 29 Mar 2005 14:42:07 +0100 Received: from d06ml068.portsmouth.uk.ibm.com (d06ml068.portsmouth.uk.ibm.com [9.149.38.194]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j2TDg774019091 for ; Tue, 29 Mar 2005 14:42:07 +0100 In-Reply-To: To: "Apache AXIS C Developers List" MIME-Version: 1.0 Subject: Re: backing up customised ant configuration X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: John Hawkins X-MIMETrack: S/MIME Sign by Notes Client on John Hawkins/UK/IBM(Release 6.0.2CF1|June 9, 2003) at 29/03/2005 14:40:39, Serialize by Notes Client on John Hawkins/UK/IBM(Release 6.0.2CF1|June 9, 2003) at 29/03/2005 14:40:39, Serialize complete at 29/03/2005 14:40:39, S/MIME Sign failed at 29/03/2005 14:40:40: The cryptographic key was not found, Serialize by Router on D06ML068/06/M/IBM(Release 6.53HF247 | January 6, 2005) at 29/03/2005 14:42:06, Serialize complete at 29/03/2005 14:42:06 Message-ID: Date: Tue, 29 Mar 2005 14:42:10 +0100 Content-Type: multipart/alternative; boundary="=_alternative 004B220C80256FD3_=" X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multipart message in MIME format. --=_alternative 004B220C80256FD3_= Content-Type: text/plain; charset="US-ASCII" +1 for using the current property based system where we can Adrian Dick/UK/IBM@IBMGB 29/03/2005 14:26 Please respond to "Apache AXIS C Developers List" To "Apache AXIS C Developers List" cc Subject Re: backing up customised ant configuration Hi, This all sounds good. I have few comments below on things that can be done for client-side testing which can help avoid this problem. I haven't (yet) tried the server-side testing, so am uncertain if it can do the same. Regards, Adrian _______________________________________ Adrian Dick (adrian.dick@uk.ibm.com) "sanjaya singharage" wrote on 29/03/2005 13:38:19: > A small ant script backupconf.xml is now created so that testers can back-up > and restore locally modified ant configurations. The targets are backup and > restore. > > What is backed up is... > 1. the server.wsdd.PLATFORM for the ant service framework Are these not generated "on-the-fly" by the ant framework? As is done when testing client-side handlers. > 2. build.PLATFORM.properties An alternative is to use -Ddir.properties= > 3. The client side test XMLs You can specify -Dtest.list= which is simply a test file with an entry for each desired .xml to be used, instead of having to delete those you're currently not interested in. > 4. The services XMLs Perhaps a similar system could be used here as in step 3. --=_alternative 004B220C80256FD3_= Content-Type: text/html; charset="US-ASCII"
+1 for using the current property based system where we can




Adrian Dick/UK/IBM@IBMGB

29/03/2005 14:26
Please respond to
"Apache AXIS C Developers List"
To
"Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
cc
Subject
Re: backing up customised ant configuration





Hi,

This all sounds good.

I have few comments below on things that can be done for client-side
testing which can help avoid this problem.  I haven't (yet) tried the
server-side testing, so am uncertain if it can do the same.

Regards,
Adrian
_______________________________________
Adrian Dick (adrian.dick@uk.ibm.com)


"sanjaya singharage" <sanjayas@opensource.lk> wrote on 29/03/2005 13:38:19:

> A small ant script backupconf.xml is now created so that testers can
back-up
> and restore locally modified ant configurations. The targets are backup
and
> restore.
>
> What is backed up is...
> 1. the server.wsdd.PLATFORM for the ant service framework
Are these not generated "on-the-fly" by the ant framework? As is done when
testing client-side handlers.

> 2. build.PLATFORM.properties
An alternative is to use -Ddir.properties=<my dir with my version of
build.PLATFORM.properties>

> 3. The client side test XMLs
You can specify -Dtest.list=<location my test.list file> which is simply a
test file with an entry for each desired <test>.xml to be used, instead of
having to delete those you're currently not interested in.

> 4. The services XMLs
Perhaps a similar system could be used here as in step 3.
--=_alternative 004B220C80256FD3_=--