Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: 32.97.182.141 is neither permitted
 nor denied by domain of suresh.thalamati@gmail.com)
Message-ID: <4260088E.9010508@gmail.com>
Date: Fri, 15 Apr 2005 11:31:42 -0700
From: Suresh Thalamati <suresh.thalamati@gmail.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: corrupt disk io storage factory for testing.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Hi,

  I  am looking at  creating a new corruptible storage factory by 
extending the engine's disk storage factory.
  Purpose of this is to do explicitly corrupt the  IO and do some 
recovery testing.  Thought ideal place
  for the corruptible storage factory is to be in the test code 
utilities not in the code line.  But  I ran into a simple obstacle ,
  constructors in the  org.apache.derby.impl.io.DirFile etc are package 
protected. So I am  unable to extend the disk storage
  factory classes successfully .

  I was  wondering  if  there was any reason for not making constructors 
public or it was just that there was not requirement to do ?
  If no one has any objections I would like  to  modify them to be 
accessible outside  org.apache.derby.impl.io.*  package ?

Thanks
-suresht