db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2469) Java Web Start JNLP PersistenceService API storage support
Date Wed, 13 Jun 2007 16:47:26 GMT

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

Kathey Marsden commented on DERBY-2469:
---------------------------------------

My opinion from Luigi's comment:
>I Consider the implementation feature-complete 95%, but I HAVE NOT DONE ANY TEST WITH
IT YET. Only unit >testing, to catch the most evident bugs/typos, but NO INTEGRATION TESTING
at all, presently. I think it will fail >horribly at start because of several reasons I
could have foreseen given my little derby experience
....

>I would also appreciate a lot code review with someone with deep knowledge about StorageFactory/StorageFile
interfaces and how should they behave

That this sounds like it is more than a day away from ready to go in.  Just my 2c.

Kathey

> 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
>             Fix For: 10.3.0.0
>
>         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.


Mime
View raw message