[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503971
]
David Van Couvering commented on DERBY-2469:
--------------------------------------------
Rats, somehow I'm missing these JIRA comments, I'll fix my filters.
Luigi, thanks for the new patch, I'll try it out. Meantime, I did the same
thing, so I'll compare and contrast.
I tried running my version under JWS and I got this error
2007-06-12 19:11:59.936 GMT
Thread[javawsApplicationMain,5,javawsApplicationThreadGroup]
java.security.AccessControlException: access denied (java.io.FilePermission
derby.log read)
Do you get this?
Also, I'm not sure what you have done to enable Derby to use this storage
factory, since you haven't added an entry for it in modules.properties (at
least you didn't in your last patch). How do you actually run and test this???
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
> 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.
