[jsr294-modularity-eg] Module Use Cases

[Peter Kriens]

On 5 mrt 2009, at 23:55, Alex Buckley wrote:

> Thanks Peter, these slides are quick and easy to digest.
> Anytime I see "container", can I think "classloader" ?
Nope, a container is more the deployment artifact. It can be  
represented by a class loader in the VM, but a class loader could load  
multiple containers.

> Siblings: module FelixSecurity and module FelixCore are packaged in  
> the same container (and probably defined by the same classloader),  
> but as you say, private modules are a benefit. Module-private types  
> in FelixSecurity are inaccessible to FelixCore, and vice-versa, right?
Yes.

> Nesting: you say "Module Systems need this". I think the OSGi module  
> system does. I do not think the Jigsaw module system does.
I think when Jigsaw grows up, you will need it as well :-( For large  
systems, the need to further partition is a very strong force. This is  
the hard to find line between simple and simplistic.

> Nesting appears orthogonal to Merging.
Yes.

Kind regards,

	Peter Kriens





>
>
> Alex
>
> Peter Kriens wrote:
>> After last call I think we need a terminology for the different  
>> ways modules can be used. At Alex request, I made this a  
>> presentation because documents over 5 pages is deemed too  
>> complicated. :-)
>> If people have more variations, or even better, actual uses cases  
>> for the different ways you can use modules, let me know. I will  
>> include them.
>> Kind regards,
>>    Peter Kriens
>> ------------------------------------------------------------------------
>> _______________________________________________
>> jsr294-modularity-eg mailing list
>> jsr294-modularity-eg at cs.oswego.edu
>> http://cs.oswego.edu/mailman/listinfo/jsr294-modularity-eg
> _______________________________________________
> jsr294-modularity-eg mailing list
> jsr294-modularity-eg at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/jsr294-modularity-eg