Reusable enterprise metadata with pattern-based structural expressions

Tilevich, Eli; Song, Myoungkyu

doi:10.1145/1739230.1739234

Cited by 8 publications

(9 citation statements)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…By relying on these domain concepts instead of on how the base program is structured, the ApprovalOfRiskyOps aspects will capture the correct set of join points upon evolution of the system, under the premise that the base code developer correctly annotates all (risky) financial operations. While the incorrect use of annotations can be a source of pointcut fragility, tools have been proposed such as [9,18] that offer support to co-evolve source code and annotations.…”

Section: Discussionmentioning

confidence: 99%

Tackling pointcut fragility with dynamic annotations

Noguera

Kellens

Deridder

et al. 2010

Proceedings of the 7th Workshop on Reflection, AOP and Meta-Data for Software Evolution

View full text Add to dashboard Cite

Within the aspect-oriented software development community, the use of annotation-based pointcuts has been proposed as a means to alleviate the fragile pointcut problem. Expressing pointcuts in terms of source-code annotations instead of the structure of the source code, decouples them from the source code of the base system and makes them more robust with respect to evolution. In this paper we demonstrate that, while annotations are suitable to capture static domain knowledge that can be leveraged by pointcut expressions, these annotations are ill-suited to capture dynamic domain knowledge. Consequently, pointcuts that rely on such dynamic knowledge still need to be defined in terms of actual source-code entities, thereby rendering them fragile again. As a means to alleviate this problem we propose Dynamic Annotations, an extension to Java annotations where the dynamic conditions under which the annotation is valid can be embedded in the annotation itself. By expressing pointcuts in terms of such dynamic annotations, these pointcuts are effectively decoupled from the structure of the base program, and become less fragile with respect to evolution. Keywords

show abstract

Section: Discussionmentioning

confidence: 99%

Tackling pointcut fragility with dynamic annotations

Noguera

Kellens

Deridder

et al. 2010

Proceedings of the 7th Workshop on Reflection, AOP and Meta-Data for Software Evolution

View full text Add to dashboard Cite

show abstract

“…Tilevich and Song [3] present meta-data invariants: an approach for documenting the naming and typing relationships between source code and annotations. To this end, their approach offers a declarative domain-specific language named MIL.…”

Section: Problem Descriptionmentioning

confidence: 99%

“…In this annotation-driven style 3 , aspects are defined as Java classes carrying annotations that map Java source code elements to AspectJ ones. An AspectJ aspect is mapped to a class carrying the @Aspect annotation, and pointcuts and advice are mapped to methods annotated with @Pointcut and either @Before, @After or @Around.…”

Section: B Pointcuts and Advice Of Aspectj5mentioning

confidence: 99%

Refactoring in the presence of annotations

Noguera

Kellens

Roover

et al. 2012

2012 28th IEEE International Conference on Software Maintenance (ICSM)

View full text Add to dashboard Cite

Abstract-Current-day programming languages include constructs to embed meta-data in a program's source code in the form of annotations. More than mere documentation, these annotations are used in modern frameworks to map sourcelevel entities to domain-specific ones. A common example being the Hibernate Object-Relational Mapping framework that relies on annotations to declare persistence configurations. While the presence of annotations extends the base semantics of the language, it also imposes restrictions on the annotated program. In this paper we consider the manner in which annotations affect automated refactorings, and in particular how they break the behavior preservation of these refactorings. As refactorings, during their condition checking phase, ignore the annotation's restrictions they can no longer guarantee the preservation of the domain-specific mappings. To address this problem, we propose to make the restrictions of the annotations explicit, and use them to steer the refactoring process. A prototype extension of the Eclipse IDE's refactoring engine is used to demonstrate our approach on three annotation libraries: Java Persistence API, AspectJ5 and Simple XML serialization.

show abstract

“…XML on the other hand is a classic form of external metadata [5,18,11]. XML allows structuring metadata and storing them externally to the source code.…”

Section: Introductionmentioning

confidence: 99%

XML to annotations mapping definition with patterns

Nosal

Porubãn

2014

COMSIS J

View full text Add to dashboard Cite

Currently, the most commonly created formal languages are configuration languages. So far source code annotations and XML are the leading notations for configuration languages. In this paper, we analyse the correspondence between these two formats. We show that there are typical XML to annotations mapping solutions (mapping patterns) that indicate a correspondence between embedded and external metadata formats in general. We argue that mapping patterns facilitate creating configuration tools and we use a case study to show how they can be used to devise a mapping between these two notations.

show abstract

Reusable enterprise metadata with pattern-based structural expressions

Cited by 8 publications

References 26 publications

Tackling pointcut fragility with dynamic annotations

Tackling pointcut fragility with dynamic annotations

Refactoring in the presence of annotations

XML to annotations mapping definition with patterns

Contact Info

Product

Resources

About