2000
DOI: 10.1007/3-540-45102-1_17
|View full text |Cite
|
Sign up to set email alerts
|

Runtime Support for Type-Safe Dynamic Java Classes

Abstract: Modern software must evolve in response to changing conditions. In the most widely used programming environments, code is static and cannot change at runtime. This poses problems for applications, that have limited down-time. More support is needed for dynamic evolution. In this paper we present an approach for supporting dynamic evolution of Java programs. In this approach, Java programs can evolve by changing their components, namely classes, during their execution. Changes in a class lead to changes in the … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
76
0
1

Year Published

2000
2000
2012
2012

Publication Types

Select...
4
4
2

Relationship

2
8

Authors

Journals

citations
Cited by 100 publications
(77 citation statements)
references
References 24 publications
0
76
0
1
Order By: Relevance
“…Dynamic ML [22] enables type-safe module replacement at runtime; changes can include the alternation of abstract types at updatetime, and the addition (and possibly removal) of module definitions via garbagecollection. Dynamic Java classes [12] offer type safety preservation but compromise portability by modifying the Java Virtual Machine; also, class replacement is not synchronized with threads using old code.…”
Section: Related Workmentioning
confidence: 99%
“…Dynamic ML [22] enables type-safe module replacement at runtime; changes can include the alternation of abstract types at updatetime, and the addition (and possibly removal) of module definitions via garbagecollection. Dynamic Java classes [12] offer type safety preservation but compromise portability by modifying the Java Virtual Machine; also, class replacement is not synchronized with threads using old code.…”
Section: Related Workmentioning
confidence: 99%
“…Bialek et al's system [6] also rewrites the updated software at the source or bytecode levels to enable its dynamic updates; however, instead of replacing classes using HotSwap, which is a standard JVM facility, their approach globally renames classes. Several approaches [17,15,11] have introduced custom virtual machines to support dynamic updates of Java applications. These approaches, however, require installing a custom JVM, which may have limited functionality and interoperability.…”
Section: Related Workmentioning
confidence: 99%
“…The details regarding this work can be found in [9,10]. While much of our work here was done to support a dynamic access control model, we believe that dynamic JVM can be used to several additional purposes, including runtime optimization, runtime code distribution and update, and hot updates.…”
Section: Dynamic Java Virtual Machinementioning
confidence: 99%