2007
DOI: 10.5381/jot.2007.6.10.a1
|View full text |Cite
|
Sign up to set email alerts
|

Reflective Constraint Management for Languages on Virtual Platforms.

Abstract: Extending an object-oriented type system with assertions makes it possible for programs using reflection to rely on semantic information to ensure correct use of discovered types. Using extended reflective capabilities to access assertions in (dynamically) loaded class objects allows a variety of general and flexible verification techniques. The XVP (Extended Virtual Platform) implements these features by extending the Java Virtual Machine with the proposed functionalities. Its architecture and applications ar… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2009
2009
2015
2015

Publication Types

Select...
3
2

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(4 citation statements)
references
References 10 publications
0
4
0
Order By: Relevance
“…Java's generic type features are quite complicated and problematic [1], unlike the C# solution [23]. There also exists an extended virtual platform for JML [20] which allows management of JML constraints. Previously developed static tools include [6].…”
Section: Extending Jml To Support Types As Theoriesmentioning
confidence: 98%
“…Java's generic type features are quite complicated and problematic [1], unlike the C# solution [23]. There also exists an extended virtual platform for JML [20] which allows management of JML constraints. Previously developed static tools include [6].…”
Section: Extending Jml To Support Types As Theoriesmentioning
confidence: 98%
“…Our most recent results that apply to XML Schema constraints and the associated transactions are based on Spec# [2]. Reflective constraint management, static and dynamic techniques for enforcing constraints, and transaction verification technology are presented in [3,4,22]. The above techniques were applied to ambients of concurrent and persistent objects in [1].…”
Section: Related Researchmentioning
confidence: 99%
“…Since the integrity constraints cannot be specified in a declarative fashion, the only option is to enforce them procedurally with nontrivial implications on efficiency and reliability. In a typed constraint-based database technology, the constraints would fit into the type systems of object-oriented languages and they should be integrated with reflective capabilities of those languages [22] so that they can be introspected at run-time. Most importantly, all of that is not sufficient if there is no technology to enforce the constraints, preferably statically, so that expensive recovery procedures will not be required when a transaction violates the constraints at run-time [2,3].…”
Section: Introductionmentioning
confidence: 99%
“…XVP [27] uses Java 5 annotations to manage assertions in a declarative form. While it improves on JML by representing assertions using reflection, it only defines two annotations (@Constraint and @Pure).…”
Section: Related Workmentioning
confidence: 99%