Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-7006

Investigate putting generated classes under the engine module loader

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 10.15.1.3
    • None
    • SQL
    • None
    • Normal

    Description

      Right now, the generated query plans are compiled into the catch-all unnamed module. This forces us to grant reflective access to several engine packages. It would be nice to encapsulate the generated classes inside the engine module loader.

      Attachments

        Issue Links

        is related to

        Improvement - An improvement or enhancement to an existing feature or task. DERBY-7012 Reduce the attack surface of the engine packages exposed by generated classes

        • Major - Major loss of function.
        • Open
        relates to

        Improvement - An improvement or enhancement to an existing feature or task. DERBY-6945 Re-package Derby as a collection of jigsaw modules

        • Major - Major loss of function.
        • Closed

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            rhillegas Richard N. Hillegas
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Slack

                Issue deployment