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 Tue, 27 Mar 2007 10:31:32 GMT

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

Luigi Lauro updated DERBY-2469:

    Attachment: SimpleStorageFactory.java

Cleaned up a bit the implementation, fixed some bugs, changed names into more suitable ones,
added more javadoc comments for SimpleStorageFactory.

JNLPStorageFactory is still very raw and untested/uncommented.

I'm currently focusing on 'finishing' my alternative BaseStorageFactory (SimpleStorageFactory)
as an abstract base class with a simpler approach for easier implementations (I will provide
a memory and JNLP one, and then the other Dir/CP/Jar could be converted into using this new
base class).

Feedback on anything VERY VERY welcome.

> 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
>            Priority: Minor
>         Attachments: JNLPStorageFactory.java, JNLPStorageFactory.java, JNLPStorageFactory.java,
SimpleStorageFactory.java, SimpleStorageFile.java, VirtualStorageFactory.java, VirtualStorageFile.java
> 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