Return-Path: Delivered-To: apmail-synapse-dev-archive@www.apache.org Received: (qmail 4338 invoked from network); 9 Aug 2009 05:03:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Aug 2009 05:03:39 -0000 Received: (qmail 25709 invoked by uid 500); 9 Aug 2009 05:03:45 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 25607 invoked by uid 500); 9 Aug 2009 05:03:45 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 25599 invoked by uid 99); 9 Aug 2009 05:03:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Aug 2009 05:03:45 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Aug 2009 05:03:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CEC7C234C004 for ; Sat, 8 Aug 2009 22:03:14 -0700 (PDT) Message-ID: <1284397817.1249794194831.JavaMail.jira@brutus> Date: Sat, 8 Aug 2009 22:03:14 -0700 (PDT) From: "Ruwan Linton (JIRA)" To: dev@synapse.apache.org Subject: [jira] Commented: (SYNAPSE-565) VFS transport should support a locking mechanism In-Reply-To: <1623135353.1249578014802.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/SYNAPSE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741023#action_12741023 ] Ruwan Linton commented on SYNAPSE-565: -------------------------------------- Implemented the ability to make the VFS file locking configurable by using a parameter named; <> which can have either "enable" or "disable" as the value. The configuration can be done at a global (sender/receiver) level and also can be overridden by the endpoint/service level. Updated the documentation as per the implementation as well. The default behaviour is to keep file locking. Thanks, Ruwan > VFS transport should support a locking mechanism > ------------------------------------------------ > > Key: SYNAPSE-565 > URL: https://issues.apache.org/jira/browse/SYNAPSE-565 > Project: Synapse > Issue Type: Improvement > Components: Transports > Affects Versions: 1.2 > Reporter: Ruwan Linton > Assignee: Ruwan Linton > Fix For: 1.3 > > > For more information please refer to; > https://wso2.org/jira/browse/ESBJAVA-602 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org For additional commands, e-mail: dev-help@synapse.apache.org