Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of paulex.yang@gmail.com
 designates 66.249.92.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=NO0d8DO5xVncxcwpxmjuLRtJuJwwpQsdsUzOVqbpXR7+M+BPkAKzLuUsjR98+xQjZ7glz+rFeN4Lj8shVMt+fmDjBihNg9koSCjuN+kjtI5Oj1x47D2KgdjnTkobn5CqtWUDb3as0seUHUz9SIUkW2zuNdNHG+miQ5POgrrHu6I=
Message-ID: <453E3A6C.704@gmail.com>
Date: Tue, 24 Oct 2006 17:08:12 +0100
From: Paulex Yang <paulex.yang@gmail.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib][luni] java.io.File bug?
References: <453879F0.9010107@gmail.com>
In-Reply-To: <453879F0.9010107@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Spark Shen wrote:
> Hi All:
>
> When login as 'root' under Linux, the following test case fails on 
> Harmony while passes on RI.
> public void test_canWrite() throws IOException{
> File f = File.createTempFile("test", null);
> f.setReadOnly();
> assertTrue(f.canWrite());
> f.deleteOnExit();
> }
> I think RI's behavior is more reasonable since the 'root' account does 
> have read/write privilege for temp files. However, Harmony only treats 
> 'root' as ordinary other users.
> It seems that similar problem happens on java.io.File.canRead().
I agree that RI's behavior is reasonable, although a little different 
with spec[1], Harmony should fix the implementation.

[1]public boolean *setReadOnly* ()
Marks the file or directory named by this abstract pathname so that only 
read operations are allowed. After invoking this method the file or 
directory is guaranteed not to change until it is either deleted or 
marked to allow write access. Whether or not a read-only file or 
directory may be deleted depends upon the underlying system.
>
> As we all know, File class deals with many different file object on 
> many different file system, would any one test File behavior on other 
> file systems.
I didn't follow, what you mean here?
>
> Best regards
>


-- 
Paulex Yang
China Software Development Lab
IBM