[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luigi Lauro updated DERBY-2469:
-------------------------------
Attachment: JNLPStorageFactory.java
VirtualStorageFile.java
VirtualStorageFactory.java
Attaching my latest versions.
I'm coding around a VirtualStorageFactory abstract class, and a
VirtualStorageFile. VirtualStorageFile implements basic logic and delegates to
VirtualStorageFactory for the actual storage manipulation.
VirtualStorageFactory base class is a reworked from scratch
'BaseStorageFactory' which instead of forcing implementors to give both
StorageFile and StorageFactory implementation, allows them only to implement a
few 'CRUD' create/delete/rename/delete methods, and build upon these to give a
working StorageFactory/StorageFile implementation.
Ideally, if things go as I plan, every storage implementation could be
re-written around this new base class if needed, or this could be used as a new
base for developing new implementations in a easier way.
Have a look at the abstract class (VirtualStorageFactory) and the delegating
implentation of StorageFile (VirtualStorageFile).
I also include a starting JNLP implementation of VirtualStorageFactory.
Javadoc comments comes mostly from interfaces (copy & paste), and VERY FEW
TESTS DONE YET, this is very alpha code, if you wanna help go through it and
suggest fixes/improvements/whatever to get things rolling for real.
P.S. Classes names are ugly, I plan to change those soon.
> 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,
> 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.
