Hi Lahiru, I've updated the code to use the airavata-server/client properties files to get any registry related settings in the absence of registry.properties file.[1]
*Note: Selecting whether to use server or client properties file is based on an system variable of which the value represents that its in server mode or client mode. This detail is accessible via the class AiravataUtils[2]. Assumption here is that server mode is established whenever a service is started up. For example look at GFacService[3] line 86.* Regards, Saminda 1. https://issues.apache.org/jira/browse/AIRAVATA-698 2. https://svn.apache.org/repos/asf/airavata/trunk/modules/commons/utils/src/main/java/org/apache/airavata/common/utils/AiravataUtils.java 3. https://svn.apache.org/repos/asf/airavata/trunk/modules/gfac-axis2/src/main/java/org/apache/airavata/services/gfac/axis2/GFacService.java On Thu, Jan 3, 2013 at 4:02 PM, Saminda Wijeratne <[email protected]>wrote: > We need to have the accessor class specified somewhere configurable... > Right now the said configurable location is a properties file called the > registry.properties... This is true for any configurable settings for a > client. > > > On Thu, Jan 3, 2013 at 3:19 PM, Lahiru Gunathilake <[email protected]>wrote: > >> Hi Devs, >> >> With latest trunk, I can see that we need a registry.properties file in in >> client side code when we use our client api, otherwise it fails in the >> following line, >> >> AiravataRegistryFactory.java: 105 with String provRegAccessorClass = >> RegistrySettings.getSetting(REGISTRY_ACCESSOR_CLASS); >> >> Do we really have to have this dependency, this is the only place which >> bothers me when I use airavata-client. >> >> Regards >> Lahiru >> >> -- >> System Analyst Programmer >> PTI Lab >> Indiana University >> > >
