Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-537 SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
  3. DERBY-538

Investigate using the standard java.net.URLClassLoader for database class loading.

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 10.3.1.4
    • Services
    • None

    Description

      Would change the fix for DERBY-537) so that's why it is a sub-task.
      Use of the standard class loader would reduce security concerns and allow jars stored in the database to take advantage of standard features such as package sealing.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. DERBY-552 Fetching resources using getResourceAsStream from a jar stored in a database that is archived in a jar file fails

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. DERBY-553 With JDK 1.5 signatures from signed jar in a database are not returned by Class.getSigners() when database in stored in a jar file.

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              djd Daniel John Debrunner
              djd Daniel John Debrunner
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: