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 188B31079E for ; Fri, 16 Aug 2013 01:40:54 +0000 (UTC) Received: (qmail 16042 invoked by uid 500); 16 Aug 2013 01:40:54 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 15914 invoked by uid 500); 16 Aug 2013 01:40:50 -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 15864 invoked by uid 99); 16 Aug 2013 01:40:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Aug 2013 01:40:50 +0000 Date: Fri, 16 Aug 2013 01:40:50 +0000 (UTC) From: "Saminda Wijeratne (JIRA)" To: dev@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AIRAVATA-893) Support for offline Schema validation for Airavata workflow Creation and Execution 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-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741800#comment-13741800 ] Saminda Wijeratne commented on AIRAVATA-893: -------------------------------------------- Hi Sanjaya, Thanks for taking initiative to fix this. Nice work on preparing the patch. I have some suggestions which you can improve on it. Apart from the improvement Suresh has mentioned do you think you can update the patch to have a order of preference of selecting online/offline automatically? The reason is that unless we educate users of this setting in the property file ("offlineModeEnabled") users may not know that they are required to update it when they loose or gain Internet connectivity. So my suggestion is let, offlineModeEnabled=auto|false|true and when "offlineModeEnabled" is "auto" (or null) check if the schema url is accessible over Internet and if not use the local schema files which you've setup. Also inorder to dynamically copy the schema files during the build time use the maven dependency plugin to retrieve the "airavata-gfac-schema-utils" jar (which will be built before any of the distributions) and extract it to a temporary location and copy the schema files using an ant task in the maven ant plugin. (Let me know if you need any help doing this) Notice that the "modules/rest/webapp" and "modules/integration-tests" will also require the schema files. > Support for offline Schema validation for Airavata workflow Creation and Execution > ---------------------------------------------------------------------------------- > > Key: AIRAVATA-893 > URL: https://issues.apache.org/jira/browse/AIRAVATA-893 > Project: Airavata > Issue Type: New Feature > Components: Airavata Client, Workflow Interpreter, XBaya > Affects Versions: 0.8 > Reporter: Mawathage Sanjaya Priyadarshana Medonsa > Priority: Minor > Fix For: WISHLIST > > Attachments: fix-AIRAVATA-893.patch > > > As per the current implementation Schema validations happens online. Internet is required to create workflows and execute them, just because of the schema validation. This could be an issue, if Internet connection is slow. Proposed solution is to introduce offline mode. If offline mode is enabled schema is validated against local schema repository. These schema validation occurs on both Airavata server and XBaya. > Schema Repository - Top Level folder schemas on each installation > Offline configuration - It could be an property on airavata client/server properties -- 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