[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503800
]
Luigi Lauro commented on DERBY-2469:
------------------------------------
Myrna:
The implementation is considered nearly feature-complete: only testing is need
to be done, but I think it will be pretty straightforward (the implementation
is simple and clean enough to sort problems quickly and easily I think).
The real work will come from improving it (linear time lookups for entities by
using indexing structures, in-memory temporary files, etc...), but a working
implementaiton is not far away IMHO.
Also, you will see an CLA very soon from Kemen, the company which I'm working
for. Later today, to be precise.
I would really like to see this make into the 10.3 time frame, especially since
it's an 'addon' to derby, and even if working so and so, would not hinder derby
in any way unless someone explicitly know about this and enable this
StorageFactory, but in the meanwhile we could have a lot more ppl test it and
provide feedback to speed up the implementation fixing and polishing.
My 2c.
> 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
> Assignee: David Van Couvering
> Priority: Minor
> Attachments: svn-diff-20070329, svn-diff-20070606
>
>
> 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.
