Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A51EBEEB7 for ; Thu, 10 Jan 2013 20:32:39 +0000 (UTC) Received: (qmail 35896 invoked by uid 500); 10 Jan 2013 20:32:39 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 35863 invoked by uid 500); 10 Jan 2013 20:32:39 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 35855 invoked by uid 99); 10 Jan 2013 20:32:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jan 2013 20:32:39 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of samindaw@gmail.com designates 209.85.215.41 as permitted sender) Received: from [209.85.215.41] (HELO mail-la0-f41.google.com) (209.85.215.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jan 2013 20:32:31 +0000 Received: by mail-la0-f41.google.com with SMTP id em20so1085415lab.14 for ; Thu, 10 Jan 2013 12:32:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=+U34lO2OyAnGkyn4eFpFAJHocv8CGs+roIf6LRC4CP8=; b=SIrmnT5Pzi+k/bawKJd1OoF30Skpw0X4MtS7bLo83//eEak0LwRQPzuPwRCPywzz5B i4WOiJ3i/3lmZYkiz47xMRi2ntrdVHxuNX8+vY6PJoZYw7vg9vdSF9bfTfw0cN6eW2+Z huJ2mtscgBAWT4qfiNqgPQfCw82HXgGk4/tPlH4PEa4WZICJrHTnzYlZVmDZ+cxbLJyk OC+RFjydHMpmHIn62Ea+V+UISpL3R0ZL/LSMe/DGrDmCO4suGI0K1g3zibIXKfyUX2+u MT6TfcE+V0QPi1mcFHTVQONRdOA+rHbP6/vtkwWXG+tE43zdU4OZzyJgLx1h0PA+St1P yYyw== Received: by 10.112.27.33 with SMTP id q1mr30720287lbg.78.1357849930949; Thu, 10 Jan 2013 12:32:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.76.136 with HTTP; Thu, 10 Jan 2013 12:31:50 -0800 (PST) In-Reply-To: References: From: Saminda Wijeratne Date: Thu, 10 Jan 2013 15:31:50 -0500 Message-ID: Subject: Re: Adding new configuration property to client side To: dev@airavata.apache.org Content-Type: multipart/alternative; boundary=bcaec554da72cae4a704d2f51250 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec554da72cae4a704d2f51250 Content-Type: text/plain; charset=ISO-8859-1 Yep... Lahiru is correct... To clarify things more.. If the settings are related to Server use ServerSettings If the settings are related to Client use ClientSettings If the settings are related to either use ApplicationSettings Saminda On Thu, Jan 10, 2013 at 2:42 PM, Lahiru Gunathilake wrote: > Hi Amila, > > I think if its onlly a client side property you need to put it in to > ClientSettings file which implement ApplicationSettings. > > I think Saminda has introduced these settings classes, Saminda Please > correct me if I am wrong. > > Regards > Lahiru > > On Wed, Jan 9, 2013 at 7:38 PM, Amila Jayasekara >wrote: > > > Hi All, > > > > What is the difference between ApplicationSettings and > > RegistrySettings classes (in terms of usage) ? > > If I want to add new property to client side (mainly to rest client > > side) which class should I use ? and which configuration files should > > I change ? > > > > Thanks > > Amila > > > > > > -- > System Analyst Programmer > PTI Lab > Indiana University > --bcaec554da72cae4a704d2f51250--