• Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.1.0, 0.2.0, 0.3, 0.4-EDR1
    • Fix Version/s: 0.5
    • Labels:


      Define and implement an updating mechanism/policies to keep changing resources up to date, e.g. countries, régions or currency data. Hereby I see the following policies:

      • LOCAL: read resources from the classpath, no automatic update (default).
      • CACHED: read resource from the CP, too, but automatically reload/update the resources using the configured connections.
        • The cache location may also be configured:
          • VM try to write the files into a locatoin within the JDK/JRE.
          • USER write the data to the user directory.
          • TEMP write the files as temporary files only and delete them on VM exit.
          • CUSTOM write the files to a custom location.

      For the second part, the locations, where the different resources can be looked up and read, can be configured. This allows clients which want to control the update mechanism (e.g. due to security reasons) to configure a local company update site, instead of directly loading the resources, e.g. from ISO, Unicode.

      The machanism implemented hereby should support the following features:

      • Each resource is defined by a resourceID and a resource location. Resources are accessed by its id.
      • It should be extendible (it can cache arbitrary resources), so it can also be used by spi implementations of this JSR.
      • The resources cached should be accessible by an API of the updater, clients should not directly access the file system.
      • Updating can be triggered programmatically.
      • There is a JMX bean that can be loaded, to trigger the update mechanism.
      • Finally it should be possible to configure some automatic updating, e.g. by using a Timer.


        There are no comments yet on this issue.


          • Assignee:
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created:

              Time Tracking

              Original Estimate - 3 days, 22 hours
              3d 22h
              Remaining Estimate - 3 days, 22 hours
              3d 22h
              Time Spent - Not Specified
              Not Specified