You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Lahiru Gunathilake <gl...@gmail.com> on 2012/10/22 16:39:03 UTC
Why do we have airavata-server.properties in number of places
Hi Suresh,
Do you know why do we have airavata-server.properties in number of packages
and I don't see xbaya.properties fields anywhere ?
Lahiru
--
System Analyst Programmer
PTI Lab
Indiana University
Re: Why do we have airavata-server.properties in number of places
Posted by Suresh Marru <sm...@apache.org>.
On Oct 22, 2012, at 10:39 AM, Lahiru Gunathilake <gl...@gmail.com> wrote:
> Hi Suresh,
>
> Do you know why do we have airavata-server.properties in number of packages
> and I don't see xbaya.properties fields anywhere ?
Lahiru,
I hope thats not the case. My whole goal with the configuration refactoring was to avoid multiple packages. Please point out which one?
./modules/distribution/src/main/resources/conf/airavata-server.properties
./modules/registry/airavata-jpa-registry/src/test/resources/airavata-server.properties
./modules/registry/airavata-registry-test/src/test/resources/airavata-server.properties
./modules/ws-messenger/messagebox/src/test/resources/airavata-server.properties
./modules/ws-messenger/messagebroker/src/test/resources/airavata-server.properties
./modules/xbaya-gui/src/main/resources/airavata-server.properties
./modules/xbaya-gui/src/test/resources/airavata-server.properties
As you can see the only version which should be modified is ./modules/distribution/src/main/resources/conf/airavata-server.properties. Rest all are within test cases and the header in the properties clearly indicate it. Note XBaya is an exception we probably should live with for this release.
The following are the xbaya.properties which are in airavata-server.properties:
###########################################################################
# Airavata Workflow Interpreter Configurations
###########################################################################
runInThread=false
provenance=true
provenanceWriterThreadPoolSize=20
gfac.embedded=false
What do you see missing?
Suresh
> Lahiru
>
> --
> System Analyst Programmer
> PTI Lab
> Indiana University