Chameleon creates "a la carte" OSGi-based application servers built around the concept of services.

The Chameleon project aims to provide a simple way to lay out specific OSGi runtimes to fit your requirements. It aims to do this by providing a layered stack. Each layer focuses on a specific part of the system, from the underlying runtime to a service catalog containing useful and reusable services.

The Chameleon service catalog lists services and their implementations. This catalog focuses on the service concept and implementations are substitutable. This means that you can choose your implementations according to your requirements and switch between them dynamically. The catalog not only contains services defined and implemented in OW2 Chameleon, but also standard OSGi services as well as other services.

The infrastructure layer contains a set of frameworks to:

  • Interact with remote services and deal with distributed event protocols
  • Introspect the current state of the system
  • (Re-) configure the system
  • Administer the system and the applications

Chameleon doesn't define one single way to deploy components, but instead supports several mechanisms such as:

  • Apache Felix FileInstall: to easily install bundles locally (like the 'deploy' folder on a JavaEE application server)
  • OSGi Bundle Repository: to deploy OSGi components and their dependencies
  • OSGi Deployment Admin: to deploy a set of OSGi bundles inside one deployment package
  • Apache Ace: to manage the deployment of a set of OSGi runtimes

Finally, Chameleon provides distributions: specific configured stacks containing a set of components selected to fit a particular domain (such as web applications or lightweight servers). When you download a distribution, you have everything you need to run the Chameleon. However, you can also extend and customize it to suit your needs.

Web site
Project leader(s)

Clement Escoffier

FunctionalityMiddleware framework / Component / Tool
License(s)Apache License 2.0
VCS repository(ies)

- type: git

Issue tracker URL
Discussion channels

Professional case studies

Open Maturity Model
Chameleon OMM
Average OMM score by category
Metrics filemetrics.json
LicenseFile countSource
Apache-2.072OW2 Fossology
No_license_found15OW2 Fossology
OFL-1.11OW2 Fossology
MIT-style1OW2 Fossology
CC-BY-3.01OW2 Fossology
Total files count: 87
Lines8,619OW2 SonarQube
Ncloc4,425OW2 SonarQube
Classes63OW2 SonarQube
Files59OW2 SonarQube
Directories12OW2 SonarQube
Functions389OW2 SonarQube
Accessors5OW2 SonarQube
Statements2,039OW2 SonarQube
Public API297OW2 SonarQube
Comment lines1,095OW2 SonarQube
Comment lines density19.8%OW2 SonarQube
Public documented API density58.9%OW2 SonarQube
Public undocumented API122OW2 SonarQube
Complexity855OW2 SonarQube
Class complexity13.6OW2 SonarQube
Function complexity2.2OW2 SonarQube
File complexity14.5OW2 SonarQube
Function complexity distributionOW2 SonarQube
File complexity distributionOW2 SonarQube
Duplicated lines182OW2 SonarQube
Duplicated blocks11OW2 SonarQube
Duplicated files5OW2 SonarQube
Duplicated lines density2.1%OW2 SonarQube
Violations211OW2 SonarQube
Blocker violations0OW2 SonarQube
Critical violations0OW2 SonarQube
Major violations115OW2 SonarQube
Minor violations96OW2 SonarQube
Info violations0OW2 SonarQube
Quality profilesOW2 SonarQube
Complexity in functions854OW2 SonarQube
False positive issues0OW2 SonarQube
Open issues211OW2 SonarQube
Reopened issues0OW2 SonarQube
Confirmed issues0OW2 SonarQube
Sqale index6dOW2 SonarQube
Ncloc language distributionOW2 SonarQube
Sqale ratingAOW2 SonarQube
Development costOW2 SonarQube
Sqale debt ratio2.2%OW2 SonarQube
OpenHub activity score2OpenHub
OpenHub one year contributor count2OpenHub
OMM configuration management0Chameleon OMM
OMM project planning0Chameleon OMM
OMM requirements1Chameleon OMM
OMM roadmap0Chameleon OMM
OMM stakeholders3Chameleon OMM
Choose a Risk Model:

Indicators Computed Score
License risk
Unique license5
Ratio no license17%
OMM License Indicator0
Quality risk
Blocker issues0
Critical issues0
Test coverage
Test success
OMM documentation1
OMM standards0
OMM testing process0
OMM software environment0
OMM commits and bug reports0
OMM maintainability and stability0
Activeness risk
OpenHub activity2
OpenHub contributor count (1 year)2
OMM configuration management0
OMM project planning0
OMM requirements1
OMM roadmap0
OMM stakeholders3