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] Commented: (DERBY-2469) Java Web Start JNLP PersistenceService API storage support
Date Wed, 13 Jun 2007 08:13:27 GMT

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

Luigi Lauro commented on DERBY-2469:

@Myrna/David regarding target 10.3: you decide guys, my focus is to get this feature done
and working in the least time possible. If putting it as experimental in 10.3 to allow more
ppl to test it up after we did some initial tests with David & CO is fine, then ok, otherwise
np, we will wait for 10.4 for having this official in derby ;-)

@David regarding enabling this feature:

David, maybe you lost some of my comments, so I repeat myself again.

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, but since the implementation is very clean and
straightforward, I'm positive that I'll be able to sort out things and make it work for real
in small time.

Presently, what I need is someone with knowledge of derby internal to tell me HOW to enable
this storagefactory with derby and test it, and maybe help me with the testing as well and
provide feedback, so that I can fix.

I would also appreciate a lot code review with someone with deep knowledge about StorageFactory/StorageFile
interfaces and how should they behave, would also really be appreciated, to get things I may
have got wrong (javadocs were not ENTIRELY clear about certain matters, and I had to 'derive'
some things from the code itself of the other factories). This can be easily done, my code
is really easy to read and understand (check and see).

@Mike regarding SVN-DIFF: AFAIK the latest svn patch (https://issues.apache.org/jira/secure/attachment/12359502/svn-diff-20070612)
should have right relative paths (example: --- /org/apache/derby/impl/io/AbstractStorageFactory.java
(revision 0)) and all the code should be JVM1.5 compliant (I removed the 1.6 stuff). Later,
I could also backport it to 1.4 (easily done), mostly by removing generics.

So please, if something is wrong with the patch let me know, so I can fix it and provide 'working'
patches in next build.

> 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
>            Assignee: David Van Couvering
>            Priority: Minor
>             Fix For:
>         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
> 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