The Pax Reflector is a application inspection tool, which can look into your running application without any special debugger. Although Pax Reflector can quite easily be used in any application, its use in OSGi environments make it even more powerful as it can be installed after the start of the main application and yet do the inspection. This could be very important when a faulty condition has occured and one need to take a closer look but can't restart the application with the debugger interface enabled.
- Pax Reflector - Details — Details about how to use Pax Reflector.
Issues, bugs, and feature requests can be submitted to the issue tracking system.
System requirements (for OSGi deployment)
Manual installation (under OSGi)
pax-run --profiles=web \
Non OSGi deployment
User guide (see resources) provides details about how to deploy Pax Reflector in non OSGi environments.
https://scm.ops4j.org/repos/ops4j/projects/pax/reflector ( or browse via FishEye )
This project builds with Apache Maven and uses Apache Felix's maven-bundle-plugin, and Peter Krien's bnd tool.
Pax Reflector reached a point where it is almost useful. It consists of 4 bundles (plan to create a uber-bundle later).
If you deploy those (pax-reflector-service, pax-reflector-servlet, pax-reflector-types, pax-reflector-html) together with Pax Web and Pax Web Extender - Whiteboard, then you have a html view into your running OSGi system.
You can also register additional Root Objects, to get a more direct line into the application.
The various "expose" attributes are not implemented yet, and future will bring a more attractive view.