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

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

Hi, Luigi.  It looks like you built this with JDK 6 and used new Java 6 methods 
such as String.isEmpty() and IOException(String message, Throwable e).   

This would mean that this functionality would *only* work in Java SE 6 VMs.  I 
think that's too restrictive, and I'm trying to adjust the code so it will 
compile under a 1.5 JDK.

Also, all of your message strings are hardcoded.  These need to be 
internationalized.  I don't believe this is a showstopper (the network client 
code was checked in with hardcoded strings -- I should know, I did the 
internationalization work), but it needs to be taken care of soon.

I'll push up a patch that includes my changes once I get this puppy to compile 
and I seem to have something working.

Thanks,

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
>
>
> 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.

Reply via email to