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] Updated: (DERBY-2469) Java Web Start JNLP PersistenceService API storage support
Date Thu, 29 Mar 2007 13:34:25 GMT

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

Luigi Lauro updated DERBY-2469:
-------------------------------

    Attachment: svn-diff-20070329

Reworked the implementation in a cleaner one.

Decided to go after a simple abstract base class (AbstractStorageFactory) similar to derby
BaseStorageFactory, but reworked it into a cleaner better version of it.

JNLPStorageFactory build upon this base class and delegates to JNLPStorageFile for actual
storage operations.

Still a lot of work to do, bear with me :)

> 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: 10.2.2.0
>         Environment: Java Web Start
>            Reporter: Luigi Lauro
>            Priority: Minor
>         Attachments: JNLPStorageFactory.java, JNLPStorageFactory.java, JNLPStorageFactory.java,
SimpleStorageFactory.java, SimpleStorageFile.java, svn-diff-20070329, VirtualStorageFactory.java,
VirtualStorageFile.java
>
>
> I would love to have Derby write/read to the storage area provided by the JNLP PersistenceService
API.
> 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
IMHO.
> 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.


Mime
View raw message