XML to annotations mapping definition with patterns

Nosal, Milan; Porubãn, Jaroslav

doi:10.2298/csis130920049n

Cited by 19 publications

(13 citation statements)

References 15 publications

(20 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Nosál et al [17,18] investigated similar abstractions but with a focus on language mapping. Denisov [8] collected requirements for configuration libraries.…”

Section: Related Workmentioning

confidence: 99%

Challenges in Validating FLOSS Configuration

Raab

Barany

2017

Open Source Systems: Towards Robust Practices

View full text Add to dashboard Cite

Abstract. Developers invest much effort into validating configuration during startup of free/libre and open source software (FLOSS) applications. Nevertheless, hardly any tools exist to validate configuration files to detect misconfigurations earlier. This paper aims at understanding the challenges to provide better tools for configuration validation. We use mixed methodology: (1) We analyzed 2,683 run-time configuration accesses in the source-code of 16 applications comprising 50 million lines of code. (2) We conducted a questionnaire survey with 162 FLOSS contributors completing the survey. We report our experiences about building up a FLOSS community that tackles the issues by unifying configuration validation with an external configuration access specification.We discovered that information necessary for validation is often missing in the applications and FLOSS developers dislike dependencies on external packages for such validations.

show abstract

“…Nosál et al [17,18] investigated similar abstractions but with a focus on language mapping. Denisov [8] collected requirements for configuration libraries.…”

Section: Related Workmentioning

confidence: 99%

Challenges in Validating FLOSS Configuration

Raab

Barany

2017

Open Source Systems: Towards Robust Practices

View full text Add to dashboard Cite

show abstract

“…The code snippets in Listing 8 show a Refers to idiom where the @Author annotation from class A is reused for class B by using a reference. @AuthorRef's value parameter 7 refers to the id parameter of the @Author annotation.…”

Section: B Idioms In Structural Relationsmentioning

confidence: 99%

“…In our previous work [7] we analyzed the correspondence between annotations and XML in the scope of configuration languages. The main manifestation of the correspondence was the discovery of a set of mapping patterns between annotations and XML.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Source Code Annotations as Formal Languages

Nosal

Sulír

Juhár

2015

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-Attribute-oriented programming (source code annotations) is a program level marking technique that enables enrichment of program elements with custom metadata. In this paper we hypothesize that there is a correspondence between source code annotations and conventional formal languages in general. We analyze our observations about source code annotations from three aspects of language description: concrete syntax, abstract syntax, and semantics. The discussion provides evidence of the hypothesized correspondence and we use it as a basis for our definition of an annotation-based language (abbreviated: @L). However, the analysis also shows that compared to conventional formal languages, source code annotations have some specificities mainly connected to their binding to host program elements. The presented analysis contributes to the field of attributeoriented programming by discussing the relationship between annotations and conventional formal languages, and by surveying relational idioms in annotations' usage that can be inspirational for annotations' authors.

show abstract

“…We designed a tool (Bridge to Equalia [4]) that provided an abstraction layer to two most common configuration formats in Java -XML and source code annotations. Bridge to Equalia (abbreviated: BTE) uses XML to annotations mapping patterns [5] to shorten the configuration interface code in cases when both annotations and XML should be accepted interchangeably. To query the annotations, BTE uses Java Reflection API in combination with the Scannotation [6] library.…”

Section: Introductionmentioning

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

XML to annotations mapping definition with patterns

Cited by 19 publications

References 15 publications

Challenges in Validating FLOSS Configuration

Challenges in Validating FLOSS Configuration

Source Code Annotations as Formal Languages

Unified Compile-Time and Runtime Java Annotation Processing

Contact Info

Product

Resources

About