Hi, Luigi. This is still in my court. I have had to focus on some
other things - constantly juggling priorities. Thanks for your
patience, and I appreciate the ping.
David
On 6/26/07, Luigi Lauro (JIRA) <[EMAIL PROTECTED]> wrote:
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508128
]
Luigi Lauro commented on DERBY-2469:
------------------------------------
Any news guys? I'm looking forward to some feedback if possible :)
Thanks again,
> 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, svn-diff-20070612
>
>
> 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.
