| 
|
QuoteRef: corwJ10_2003
ThesaHelp:
ACM references a-e
Topic:
deployable module or assembly
Topic:
programming with a database of modules
Topic:
software components
Topic:
import/export lists for defining an interface
Topic:
security by seal
Topic:
opaque and partially-opaque data types
Reference
Corwin, J., Bacon, D.F., Grove, D., Murthy, C., "MJ: a rational module system for Java and its applications", OOPSLA2003 18th Conference on Object Oriented Programming, Systems, Languages, and Applications, Anaheim California USA, October 2003, ACM SIGPLAN, pp. 241-254. Google
abstract ;;Quote: use MJ module system to avoid complex CLASSPATH definitions in existing applications; functionally identical, handles different versions, enables optimizations
245 ;;Quote: MJ module component registry with import/export lists, access control, and initialization code
246 ;;Quote: use seal and unseal to control subclassing; by class or package
249 ;;Quote: pass-through modules necessary for module security; e.g., hide an internal module or aggregate a collection of module interfaces
ThesaHelp: ACM references a-e (259 items)
Topic: deployable module or assembly (10 items)
Topic: programming with a database of modules (94 items)
Topic: software components (11 items)
Topic: import/export lists for defining an interface (20 items)
Topic: security by seal (16 items)
Topic: opaque and partially-opaque data types (14 items)