db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-7006) Investigate putting generated classes under the engine module loader
Date Thu, 11 Oct 2018 13:37:00 GMT

     [ https://issues.apache.org/jira/browse/DERBY-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Hillegas updated DERBY-7006:
---------------------------------
    Attachment: derby-7006-01-ac-alanBateman.diff

> Investigate putting generated classes under the engine module loader
> --------------------------------------------------------------------
>
>                 Key: DERBY-7006
>                 URL: https://issues.apache.org/jira/browse/DERBY-7006
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.15.0.0
>            Reporter: Rick Hillegas
>            Priority: Major
>         Attachments: derby-7006-01-aa-remiForax.diff, derby-7006-01-ac-alanBateman.diff
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message