Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Received-SPF: pass (nike.apache.org: domain of thejaka.amila@gmail.com
 designates 209.85.214.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CANotcz6Vit6bFJppgrAtVTyNW1qK3DjjQNRON2dPELyGk1BQyw@mail.gmail.com>
References: 
 <CANotcz6Vit6bFJppgrAtVTyNW1qK3DjjQNRON2dPELyGk1BQyw@mail.gmail.com>
Date: Thu, 6 Mar 2014 13:55:14 -0500
Message-ID: 
 <CAKUcLKbm3TpT25akzHFfuPxwG5teQ3aehDHaREFS-K0KuEduAA@mail.gmail.com>
Subject: Re: Suggestions on maintaining the server/client configuration files?
From: Amila Jayasekara <thejaka.amila@gmail.com>
To: dev <dev@airavata.apache.org>
Content-Type: multipart/alternative; boundary=089e013d0d6c74b3e404f3f4ad33

--089e013d0d6c74b3e404f3f4ad33
Content-Type: text/plain; charset=ISO-8859-1

Hi Saminda,

I guess the best thing is to create template configuration files in a
central location and replace needed variables within the test
initialization and place generated config files within the target directory
of the test case.

E.g :- registry.url = ${registry.url}

${registry.url} is replaced within the test case with appropriate value.
Then we dont need to duplicate configuration files in everywhere. Also when
a configuration is updated we only need to change in a single place.
You may encapsulate template parameter replacing logic into a common util
class so that each test case can just invoke the logic.

Further we should have a single place to read all configurations and all
subcomponents must go through this configuration component to get config
values. Otherwise it will be hard to maintain the configuration reading
code.

Thanks
Amila


On Thu, Mar 6, 2014 at 1:38 PM, Saminda Wijeratne <samindaw@gmail.com>wrote:

> There are several places which we need the airavata-server.properties and
> airavata-client.properties files to be present in order to run tests and
> standalone servers resulting in replication. Any idea how we should handle
> this?
>

--089e013d0d6c74b3e404f3f4ad33
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Saminda,<div><br></div><div>I guess the best thing is t=
o create template configuration files in a central location and replace nee=
ded variables within the test initialization and place generated config fil=
es within the target directory of the test case.=A0</div>
<div><br></div><div>E.g :- registry.url =3D ${registry.url}</div><div><br><=
/div><div>${registry.url} is replaced within the test case with appropriate=
 value. Then we dont need to duplicate configuration files in everywhere. A=
lso when a configuration is updated we only need to change in a single plac=
e.=A0</div>
<div>You may encapsulate template parameter replacing logic into a common u=
til class so that each test case can just invoke the logic.</div><div><br><=
/div><div>Further we should have a single place to read all configurations =
and all subcomponents must go through this configuration component to get c=
onfig values. Otherwise it will be hard to maintain the configuration readi=
ng code.</div>
<div><br></div><div>Thanks</div><div>Amila</div></div><div class=3D"gmail_e=
xtra"><br><br><div class=3D"gmail_quote">On Thu, Mar 6, 2014 at 1:38 PM, Sa=
minda Wijeratne <span dir=3D"ltr">&lt;<a href=3D"mailto:samindaw@gmail.com"=
 target=3D"_blank">samindaw@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">There are several places wh=
ich we need the airavata-server.properties and airavata-client.properties f=
iles to be present in order to run tests and standalone servers resulting i=
n replication. Any idea how we should handle this?<br>


</div>
</blockquote></div><br></div>

--089e013d0d6c74b3e404f3f4ad33--