[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2469:
----------------------------------
It is up to you if you want to make the code buildable under 1.4. I think this
will allow for a wider audience, especially if there are
no real dependencies on post 1.4 features. All that I am looking for is that
any checkin, do the appropriate thing to the ant build
files so that if a developer only has jdk1.4 that the system won't try to build
this code. I believe the current requirement for trunk
and 10.3 is that the system should build cleanly and run tests cleanly for
jdk1.4..2 jvm's. It may not build all classes, and may not
run all code (ie. jdbc4.0) testing.
I believe the following shows build/tests for both building against
jdk1.4/running various jvm's and building against 1.6 :
http://dbtg.thresher.com/derby/test/
Once the build changes are made, I would be happy to try out the patch and
verify it does not cause build errors in a 1.4 only system,
as that is the environment I tend to run in.
> 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.
