1998
DOI: 10.1145/286942.286945
|View full text |Cite
|
Sign up to set email alerts
|

Dynamic class loading in the Java virtual machine

Abstract: Class loaders are a powerful mechanism for dynamically loading software components on the Java platform.They are unusual in supporting all of the following features:laziness, type-q? linkage, user-defined extensibility, and multiple communicating namespaces.We present the notion of class loaders and demonstrate some of their interesting uses. In addition, we discuss how to maintain type safety in the presence of user-defined dynamic class loading.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
86
0

Year Published

2000
2000
2015
2015

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 104 publications
(86 citation statements)
references
References 7 publications
0
86
0
Order By: Relevance
“…[4,1,6,9]). Software components can be rebound on-the-fly, using a mechanism of dynamic class loading and linking [10,15].…”
Section: Introductionmentioning
confidence: 99%
“…[4,1,6,9]). Software components can be rebound on-the-fly, using a mechanism of dynamic class loading and linking [10,15].…”
Section: Introductionmentioning
confidence: 99%
“…Recall that a Java class type is uniquely determined by the combination of a class loader and a fully qualified class name [18]. In response to changes in the deployment directory, JBoss instantiates class loaders to dynamically define new class types, which may correspond to "new versions" of previously defined class types.…”
Section: Deployment and Undeploymentmentioning
confidence: 99%
“…Components loaded from different deployment units may contain classes with the same name, but these classes will be treated as different types by the Java virtual machine [18]. This approach avoids class clashes between deployment units, but hinders interactions between separately deployed parts.…”
Section: Class Loading Issuesmentioning
confidence: 99%
“…Or how can an application determine whether the module to be retrieved is already loaded and initialized or not? The first question is targeting a basic problem of the original class loader approach of Java which does not allow loading two classes having the same fully-qualified class name (FQCN) by the same class loader [25]. Thus, in order to support the composition of modules in different variants within the same JVM, we have to use and manage several class loaders.…”
Section: Fig 8 Module Deployment Using Class Collectionsmentioning
confidence: 99%