db-derby-dev mailing list archives

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

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

David Van Couvering commented on DERBY-2469:
--------------------------------------------

OK, here is my proposal:

- Let's not try to shove it into this release
- Let's get this checked in very soon so people can start playing with it.  
- What I would *like* is if our nightly builds are easily available off of the web.  How hard
is this to do?  But that's a separate discussion, and I'll re-ask this question on derby-dev
- I'll put it into the experimental directory and have it build for JDK 1.5 or above, into
derby-experimental.jar
- Should the package name be org.apache.derby.impl.io.jnlp or org.apache.derby.jnlp?  I'm
leaning for the former, as it is an IO implementation.
- I woud like to check this in (after Friday) so that it builds, but without unit tests. 
That way Luigi and I and others can collaborate better on adding appropriate testing
- The goal is that hopefully once this is seen to be working and useful, we can migrate the
package from the experimental tree to the main tree (and into derby.jar), and integrate the
unit tests into the full regression suite.

Does this sound like a plan?

Luigi, I have a *fair* idea how to run this within Derby, but I'm still testing this out.
 What I want to know is how you tested it at all?  How did you test this *outside* of Derby?
 If you have JUnit unit tests for this, let's have them, being able to run unit tests for
these classes independent of Derby IMHO is a Good Thing.  You can ask the list where the unit
tests should go, I'm not too clear on that myself, but at a minimum just post them as a jar
file to this JIRA so we can have a look at them.

David

> 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