Analyzing Program Dependencies in Java EE Applications

Shatnawi, Anas; Mili, Hafedh; Boussaidi, Ghizlane El; Boubaker, Anis; Guéhéneuc, Yann‐Gaël; Moha, Naouel; Privat, Jean; Abdellatif, Manel

doi:10.1109/msr.2017.6

Cited by 15 publications

(7 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Thus, we need to examine the different technologies and figure out how that invocation works. In [19] [20], we examined, among other things, invocation patterns for JSP, and identified half a dozen ways that a JSP page can be invoked 9 , including:…”

Section: Characterizing and Codifying Invocation Patternsmentioning

confidence: 99%

See 1 more Smart Citation

Service-Oriented Re-engineering of Legacy JEE Applications: Issues and Research Directions

Mili,

El-Boussaidi,

Shatnawi

et al. 2019

Preprint

Self Cite

View full text Add to dashboard Cite

Service-orientation views applications as orchestrations of independent software services that (1) implement functions that are reusable across many applications, (2) can be invoked remotely, and ( 3) are packaged to decouple potential callers from their implementation technology. As such, it enables organizations to develop quality applications faster than without services.Legacy applications are not service-oriented. Yet, they implement many reusable functions that could be exposed as services. Organizations face three main issues when re-engineering legacy application to (re)use services: (1) to mine their existing applications for reusable functions that can become services, (2) to package those functions into services, and (3) to refactor legacy applications to invoke those services to ease future maintenance.In this paper, we explore these three issues and propose research directions to address them. We choose to focus on the service-oriented re-engineering of recent legacy object-oriented applications, and more specifically, on JEE applications, for several reasons. First, we wanted to focus on architectural challenges, and thus we choose to not have to deal with programming language difference between source and target system. We chose JEE applications, in particular, because they embody the range of complexities that one can encounter in recent legacy applications, namely, multi-language systems, multi-tier applications, the reliance on external configuration files, and the reliance on frameworks and container services during runtime. These characteristics pose unique challenges for the three issues mentioned above.

show abstract

Section: Characterizing and Codifying Invocation Patternsmentioning

confidence: 99%

“…Similar analyses need to be made for other JEE technologies, including Java Server Faces (see [19] and [20]). For the purpose of this project,we will not perform an exhaustive analysis of all the technologies.…”

Section: Characterizing and Codifying Invocation Patternsmentioning

confidence: 99%

Service-Oriented Re-engineering of Legacy JEE Applications: Issues and Research Directions

Mili,

El-Boussaidi,

Shatnawi

et al. 2019

Preprint

Self Cite

View full text Add to dashboard Cite

show abstract

“…Recently developed software systems contains implicit dependencies resulted form the use of late dynamic-binding, Java-reflection and container-services offered by the frameworks. These implicit dependencies are difficult to be detected using static analysis techniques [27]. All of these existing component identification approaches that are designed to identify components from OO software applications are not be directly applied to OO APIs.…”

Section: Related Workmentioning

confidence: 99%

Identifying software components from object-oriented APIs based on dynamic analysis

Shatnawi

Shatnawi²,

Saied

et al. 2018

Proceedings of the 26th Conference on Program Comprehension

Self Cite

View full text Add to dashboard Cite

The reuse at the component level is generally more effective than the one at the object-oriented class level. This is due to the granularity level where components expose their functionalities at an abstract level compared to the fine-grained object-oriented classes. Moreover, components clearly define their dependencies through their provided and required interfaces in an explicit way that facilitates the understanding of how to reuse these components. Therefore, several component identification approaches have been proposed to identify components based on the analysis object-oriented software applications. Nevertheless, most of the existing component identification approaches did not consider co-usage dependencies between API classes to identify classes/methods that can be reused to implement a specific scenario. In this paper, we propose an approach to identify reusable software components in object-oriented APIs, based on the interactions between client applications and the targeted API. As we are dealing with actual clients using the API, dynamic analysis allows to better capture the instances of API usage. Approaches using static analysis are usually limited by the difficulty of handling dynamic features such as polymorphism and class loading. We evaluate our approach by applying it to three Java APIs with eight client applications from the DaCapo benchmark. DaCapo provides a set of pre-defined usage scenarios. The results show that our component identification approach has a very high precision.

show abstract

“…With regards to dependency modeling approaches, Shatnawi et al aim at identifying dependency call graphs of legacy Java EE applications to ease their migration to loosely coupled architectures [39]. Kula et al also study JVM-based projects to support migration to more recent versions of a given open source library [28].…”

Section: Related Workmentioning

confidence: 99%

“…Nevertheless, manifold dependencies are not only specified in source code but also in configuration files. To face this challenge, both approaches parse dependencies from these sources and extract information in their own models: the Knowledge Discovery Meta-model (KDM) [34,39] and the Software Universe Graph (SUG) [28]. Jezek et al statically extract dependencies and potential smells from the source code and bytecode of applications [20].…”

Section: Related Workmentioning

confidence: 99%

An empirical evaluation of OSGi dependencies best practices in the eclipse IDE

Ochoa

Degueule

Vinju

2018

Proceedings of the 15th International Conference on Mining Software Repositories

View full text Add to dashboard Cite

OSGi is a module system and service framework that aims to fill Java's lack of support for modular development. Using OSGi, developers divide software into multiple bundles that declare constrained dependencies towards other bundles. However, there are various ways of declaring and managing such dependencies, and it can be confusing for developers to choose one over another. Over the course of time, experts and practitioners have defined "best practices" related to dependency management in OSGi. The underlying assumptions are that these best practices (i) are indeed relevant and (ii) help to keep OSGi systems manageable and efficient. In this paper, we investigate these assumptions by first conducting a systematic review of the best practices related to dependency management issued by the OSGi Alliance and OSGi-endorsed organizations. Using a large corpus of OSGi bundles (1,124 core plug-ins of the Eclipse IDE), we then analyze the use and impact of 6 selected best practices. Our results show that the selected best practices are not widely followed in practice. Besides, we observe that following them strictly reduces classpath size of individual bundles by up to 23% and results in up to ±13% impact on performance at bundle resolution time. In summary, this paper contributes an initial empirical validation of industry-standard OSGi best practices. Our results should influence practitioners especially, by providing evidence of the impact of these best practices in real-world systems.

show abstract

Analyzing Program Dependencies in Java EE Applications

Cited by 15 publications

References 14 publications

Service-Oriented Re-engineering of Legacy JEE Applications: Issues and Research Directions

Service-Oriented Re-engineering of Legacy JEE Applications: Issues and Research Directions

Identifying software components from object-oriented APIs based on dynamic analysis

An empirical evaluation of OSGi dependencies best practices in the eclipse IDE

Contact Info

Product

Resources

About