A way to opt out of access restrictions on non-exported members.
ali.ebrahimi1781 at gmail.com
Wed Nov 18 12:27:58 UTC 2015
On Wed, Nov 18, 2015 at 2:38 PM, Alan Bateman <Alan.Bateman at oracle.com>
> On 18/11/2015 10:55, Ali Ebrahimi wrote:
> Is there other options? (non-command-line options)
> As I said in one of the previous mails, there are a number of things that
> can be explored. The EE container creating the configuration can control
> the exports, it can completely override module declarations if it really
> wants to. Another option might be wrapping the entry point so that the any
> additional exports are set when the container is launching the application.
> I think we should be confident that we can work through all these issues
> and come up with the right solutions.
I think we need some friend (or privileged or trusted or bootstrapper)
module concept that have full access for all modules in configuration that
this module created.
bootstrapper module == configuration creator module
This can be used for all containers (EE or OSGI or Spring, ..., even my toy
More information about the jigsaw-dev