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 DCA11E84D for ; Fri, 25 Jan 2013 05:29:39 +0000 (UTC) Received: (qmail 60208 invoked by uid 500); 25 Jan 2013 05:29:39 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 60110 invoked by uid 500); 25 Jan 2013 05:29: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 60063 invoked by uid 99); 25 Jan 2013 05:29:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jan 2013 05:29:39 +0000 Date: Fri, 25 Jan 2013 05:29:39 +0000 (UTC) From: "Suresh Marru (JIRA)" To: dev@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (AIRAVATA-643) Add different registry accessors to airavata-server.properties and update AiravataJPARegistry accordingly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRAVATA-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Marru closed AIRAVATA-643. --------------------------------- Closing the resolved issue. > Add different registry accessors to airavata-server.properties and update AiravataJPARegistry accordingly > --------------------------------------------------------------------------------------------------------- > > Key: AIRAVATA-643 > URL: https://issues.apache.org/jira/browse/AIRAVATA-643 > Project: Airavata > Issue Type: Bug > Components: Registry API > Affects Versions: 0.5 > Reporter: Chathuri Wimalasena > Assignee: Chathuri Wimalasena > Fix For: 0.6 > > > Users can have their own provenance registry, project registry and other types of registry implementations. We should check whether such registry implementation is available before calling the default implementation in airavata -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira