New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add some benefits over other concepts like DS, BluePrint, ... #1

Open

lefou opened this issue Feb 6, 2019 · 0 comments

Member

lefou commented Feb 6, 2019 •

edited

Loading

Benefits over pure Java Activator
** Better code
Benefits over DS, Blueprint ...
** when using pure DS/Blueprint:
*** no XML writing
** when using Annotation-based DB/Blueprint:
*** no usage specific annotations on usage un-specific classes
** No extra post-processing step needed, e.g. a bnd plugin that scans annotation and/or XML files
** Full support via IDE and Compiler
** Bnd will not miss imports
** Out-of-the-box lifecycle dynamics outside of OSGi Container, e.g. with Felix Connect (former PojoSR)
** Easy Unit-Testing of Activator functionality in standard unit tests
** Ideomatic Java and Scala notation, without Annotations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment