Dynamic modules and bidirectional interoperation

[mark.reinhold at oracle.com]

2016/10/7 8:47:53 -0700, tjwatson at us.ibm.com:
> Overall I think this approach with #NonHierarchicalLayers is worth 
> pursuing.  A couple of observations.
> 
> 1) Any OSGi dependencies that influence class loader delegation will not 
> be declared in the ModuleDescriptors which represent the OSGi bundle 
> wirings.  Instead we will depend on the ability to 
> #ReadabilityAddedByLayerCreator to wire up the modules within the bundle 
> Layer according to OSGi resolution rules.

A question for you about #ReadabilityAddedByLayerCreator ...

In this approach, will the code that creates a per-bundle layer be
able to specify all of the required reads edges at the time at which
that layer is created?  Or will it need to be able to add reads edges
at one or more later times?

If the answer is the former then the resulting API is likely to be
much simpler.

- Mark