dc.contributor.author |
Renaud, K
|
|
dc.contributor.editor |
Renaud, K.
|
|
dc.contributor.editor |
Kotze, P
|
|
dc.contributor.editor |
Barnard, A
|
|
dc.date.accessioned |
2018-08-23T10:57:58Z |
|
dc.date.available |
2018-08-23T10:57:58Z |
|
dc.date.issued |
2001 |
|
dc.identifier.citation |
Renaud, K. (2001) JavaCloak - considering the limitations of proxies for facilitating Java runtime specialisation. Hardware, Software and Peopleware: Proceedings of the Annual Conference of the South African Institute of Computer Scientists and Information Technologists, University of South Africa, Pretoria, 25-28 September 2001 |
en |
dc.identifier.isbn |
1-86888-195-4 |
|
dc.identifier.uri |
http://hdl.handle.net/10500/24772 |
|
dc.description.abstract |
This paper discusses issues pertaining to mechanisms which can be used to change the behaviour of Java classes at runtime. The proxy mechanism will be compared to and contrasted with other standard approaches to this problem. Some of the problems the proxy mechanism is subject to will be expanded upon. The question of whether statically developed proxies are a viable alternative to bytecode rewriting was investigated by means of the JavaCloak system, which uses statically-generated proxies to alter the run-time behaviour of externally-developed code. The issues addressed in this paper include ensuring type safety, dealing with the self problem, object encapsulation, and issues
of object identity and equality. Some performance figures are provided which demonstrate the load the JavaCloak proxy mechanism places on the system. |
en |
dc.language.iso |
en |
en |
dc.subject |
Reflection |
en |
dc.subject |
Java |
en |
dc.subject |
Proxies |
en |
dc.subject |
JavaCloak |
en |
dc.subject |
Runtime specialisation |
en |
dc.title |
JavaCloak - considering the limitations of proxies for facilitating Java runtime specialisation |
en |