Hi Nirmal,
ImportExportProcedureTest is a good place to start. Others should turn
up if you grep the tests for extinout.
Hope this helps,
-Rick
Nirmal Fernando wrote:
Hi Rick,
Thanks for the reply.
If you don't mind please tell me some test files that are using the
testing framework's extinout directory?
Thanks.
On Thu, Jul 8, 2010 at 9:40 PM, Rick Hillegas <[email protected]> wrote:
Hi Nirmal,
If the new i/o call is in code which is in the derbytools jar file, then you
need to add an i/o permission to the derbytools block of permissions in
derby_tests.policy. You can use one of the existing permissions there as a
template. Note that you may not need to add a new permission. That policy
file already grants the tools read/write/delete access to the testing
framework's extinout directory. Provided that your test does its i/o to that
directory (as other tests do), the existing permission should cover you.
Hope this helps,
-Rick
Nirmal Fernando wrote:
Yeah, Knut I think you're right.
But how can I add a new permission?
On Thu, Jul 8, 2010 at 8:43 PM, Knut Anders Hatlen
<[email protected]> wrote:
Nirmal Fernando <[email protected]> writes:
I'm getting following error stack trace while trying to read a content
of a file inside the class "XplainStatisticsTest.java".
How can I grant the permission to read these files to Derby?
Perhaps more liberal permissions are needed in derby_tests.policy found
in the functionTests/util directory?
--
Knut Anders
