Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Tue, 5 Feb 2013 08:06:12 +0000 (UTC)
From: "Jean-Marc Borer (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12630825.1360051523662.245591.1360051572721@arcas>
In-Reply-To: <JIRA.12630825.1360051523662@arcas>
References: <JIRA.12630825.1360051523662@arcas>
Subject: [jira] [Created] (VFS-452) FileObject read/write attributes should
 reflect underlying FileSystem capabilities
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jean-Marc Borer created VFS-452:
-----------------------------------

             Summary: FileObject read/write attributes should reflect underlying FileSystem capabilities
                 Key: VFS-452
                 URL: https://issues.apache.org/jira/browse/VFS-452
             Project: Commons VFS
          Issue Type: Bug
    Affects Versions: 2.0
            Reporter: Jean-Marc Borer


When you do a:
FileObject fo = fsManager.resolveFile("http://host:port/somefile.xml");
VFS will create a HTTP FileSystem that has only read capabilities. However, fo.isWritable() returns true where
fo.getFileSystem().hasCapability(Capability.WRITE_CONTENT)); return false as expected.

This is inconsistent in my opinion and should be fixed or is it intentionally implemented that way?
  

--
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