[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Van Couvering updated DERBY-2469:
---------------------------------------
Attachment: jnlptest.jar
This is a NetBeans project (using NetBeans 6) that attempts to use the JNLP
storage provider and it fails (see exception below). I'm not sure if the
failure is because of no suitable driver or because the attempt to ready
derby.log hit an AccessControlException, which then caused the no suitable
driver exception (I'm suspecting the latter).
You can build this independent of NetBeans using Ant, but if you want to test,
I highly recommend getting the latest milestone of NetBeans 6,
which can be found at
http://dlc.sun.com/netbeans/download/6.0/milestones/latest/
Error messages:
2007-06-26 16:59:33.189 java[1746] CFLog (0): CFMessagePort:
bootstrap_register(): failed 1103 (0x44f), port = 0xf503, name =
'java.ServiceProvider'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2007-06-26 16:59:33.190 java[1746] CFLog (99): CFMessagePortCreateLocal():
failed to name Mach port (java.ServiceProvider)
2007-06-26 23:59:36.986 GMT
Thread[javawsApplicationMain,5,javawsApplicationThreadGroup]
java.security.AccessControlException: access denied (java.io.FilePermission
derby.log read)
java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:545)
at java.sql.DriverManager.getConnection(DriverManager.java:193)
at testjnlp2.Main.main(Main.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.javaws.Launcher.executeApplication(Launcher.java:1161)
at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1108)
at com.sun.javaws.Launcher.continueLaunch(Launcher.java:951)
at com.sun.javaws.Launcher.handleApplicationDesc(Launcher.java:522)
at com.sun.javaws.Launcher.handleLaunchFile(Launcher.java:218)
at com.sun.javaws.Launcher.run(Launcher.java:165)
at java.lang.Thread.run(Thread.java:613)
> 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: jnlptest.jar, svn-diff-20070329, svn-diff-20070606,
> svn-diff-20070612, svn-diff-20070626
>
>
> 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.
