db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luigi Lauro (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2469) Java Web Start JNLP PersistenceService API storage support
Date Tue, 12 Jun 2007 09:18:26 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503790

Luigi Lauro commented on DERBY-2469:

Known issues and missing tidbits:

0) NO TESTING (except very basic ones) DONE. Handle with care and give me feedback, so I can
fix ;-)

1) StorageFile.renameTo() not implemented yet (will do soon, it's easy enough). Hope derby
can work without rename, in a fresh environment ;-)

2) Check if PersistenceService implementation is meant to be thread-safe or not: currently
my code do not synchronize in the StorageFile.createNewFile(), but this will need to be done,
if PersistenceService does not give thread-safety guarantees. Probably, other methods will
need to be synchronized as well.

3) RandomAccess not implemented: to do it, sooner or later.

4) Temporary files uses persistent entities: convert these to in-memory entities, to avoid
using useful JNLP PersistenceService space and spamming the persistent entities list with
temp files. Currently they are implemented using JNLP Persistent entities like normal files.

5) I18N: to be done, will be last thing, when everything else is working.

> Java Web Start JNLP PersistenceService API storage support
> ----------------------------------------------------------
>                 Key: DERBY-2469
>                 URL: https://issues.apache.org/jira/browse/DERBY-2469
>             Project: Derby
>          Issue Type: New Feature
>          Components: Store
>    Affects Versions:
>         Environment: Java Web Start
>            Reporter: Luigi Lauro
>            Assignee: David Van Couvering
>            Priority: Minor
>             Fix For:
>         Attachments: svn-diff-20070329, svn-diff-20070606
> I would love to have Derby write/read to the storage area provided by the JNLP PersistenceService
> Since Derby is now bundled with the Java6 JDK as JavaDB, I think this  integration would
go a long way towards making derby more developer- friendly in Java Web Start environments,
where using the sandbox tools Sun provides us it the right way to go, instead of working 
around it and force the user to give the app the authorization to write on the hard drive
> I'm investigating the effort needed to provide an implementation of the WritableStorageFactory
interface around the PersistenceService API, and if that's doable in a few days work, I will
start working on it and submit a patch for testing/approval ASAP.
> Feel free to volounteer and provide pointers/hints/whatever, it's really appreciate,
especially since I currently know nothing of derby internals.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message