Annotation Framework Validation Using Domain Models

Noguera, Carlos; Duchien, Laurence

doi:10.1007/978-3-540-69100-6_4

Cited by 17 publications

(10 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This allows the annotation developer to express constraints on the characteristics of the source-code entities that carry annotations. AVal [23], [24] offers a set of meta-annotations to express both dependencies between annotations and dependencies between annotations and the source code entities on which they lay. Additional constraints can be expressed using OCL queries over a meta-model of the source code.…”

Section: Discussionmentioning

confidence: 99%

Co-evolving Annotations and Source Code through Smart Annotations

Kellens

Noguera

Schutter

et al. 2010

2010 14th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

Abstract-Annotations are a means to attach additional meta data to the source code of a system. Nowadays, more and more technologies rely on the presence of such annotations in the source code: beyond their use for documentation purposes, annotations impact the behaviour of the system. Since there exists little or no support to make sure that upon evolution of the system, the source code remains correctly annotated, source code can become miss-annotated. This in turn, can result in erroneous behaviour. In this paper we present Smart Annotations, an approach for co-evolving source code and annotations. Our approach enables developers to constrain the use of annotations in the source code and offers tool support to identify conflicts between source code and annotations. To illustrate the use of our approach, we demonstrate its applicability using examples from the domain of aspect-oriented programming and Enterprise Java Beans.

show abstract

Section: Discussionmentioning

confidence: 99%

Co-evolving Annotations and Source Code through Smart Annotations

Kellens

Noguera

Schutter

et al. 2010

2010 14th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

show abstract

“…Noguera has a similar approach to Cepa in his tool AVal [23], [24], which is used to validate frameworks that are using annotations. Purpose of this validation is checking, whether the framework uses specific annotations in a correct way.…”

Section: Related Workmentioning

confidence: 99%

Unified Compile-Time and Runtime Java Annotation Processing

Pigula

Nosal

2015

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-Java provides two different options for processing source code annotations. One of them is the annotation processing API used in compile time, and the other is the Reflection API used in runtime. Both options provide different API for accessing program metamodel. In this paper, we examine the differences between those representations and we discuss options on how to unify these models along with advantages and disadvantages of this approach. Based on this proposal, we design a unified Java language model and present a prototype tool which can populate a unified model during both compilation and runtime. The paper includes the designed API of this unified language model. To verify our approach, we have performed experiments to show the usability of the unified metamodel.

show abstract

“…An automated, user-extensible tool reports the cases when the verified source code violates any restrictions or dependencies. Noguera et al [19] enhance annotation declarations with meta-annotations that define various constraints to check the correctness of using annotations. The constraints, expressed as Object Constraint Language queries, must be satisfied whenever the corresponding annotations appear in the program.…”

Section: A Validation For Metadatamentioning

confidence: 99%

Metadata invariants: Checking and inferring metadata coding conventions

Song

Tilevich

2012

2012 34th International Conference on Software Engineering (ICSE)

View full text Add to dashboard Cite

Abstract-As the prevailing programming model of enterprise applications is becoming more declarative, programmers are spending an increasing amount of their time and efforts writing and maintaining metadata, such as XML or annotations. Although metadata is a cornerstone of modern software, automatic bug finding tools cannot ensure that metadata maintains its correctness during refactoring and enhancement. To address this shortcoming, this paper presents metadata invariants, a new abstraction that codifies various naming and typing relationships between metadata and the main source code of a program. We reify this abstraction as a domain-specific language. We also introduce algorithms to infer likely metadata invariants and to apply them to check metadata correctness in the presence of program evolution. We demonstrate how metadata invariant checking can help ensure that metadata remains consistent and correct during program evolution; it finds metadata-related inconsistencies and recommends how they should be corrected. Similar to static bug finding tools, a metadata invariant checker identifies metadata-related bugs as a program is being refactored and enhanced. Because metadata is omnipresent in modern software applications, our approach can help ensure the overall consistency and correctness of software as it evolves.

show abstract

Annotation Framework Validation Using Domain Models

Cited by 17 publications

References 9 publications

Co-evolving Annotations and Source Code through Smart Annotations

Co-evolving Annotations and Source Code through Smart Annotations

Unified Compile-Time and Runtime Java Annotation Processing

Metadata invariants: Checking and inferring metadata coding conventions

Contact Info

Product

Resources

About