Hi List, While going through the code, Ivo and I noticed that there are several mechanisms used to provide libraries (such as OpenSesame and Cassandra) with their storage directories. Most often, they will have some configured property, which is used to initialize the underlying library. Changing this setting usually has bad results: the library can no longer find the files it needs.
We believe this is a general issue: some services will need storage that is more persistent than the bundle cache, but is easily manageable by the services that need the storage. We could, for instance, create a service that has the duty of keeping track of storage directories for given services, and perhaps can even move them around; file-persistence-requiring bundles can then use this service, and get a File object that points them to the directory they can use. For now, we resorted to hardcoding the paths in the bundles, since the configuration-option didn't work anyway. Any other thoughts? Angelo & Ivo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.amdatu.org/pipermail/amdatu-developers/attachments/20101008/2fcab847/attachment.html
