Search for bundles, decompile classes, view services and quickly enter configurations. Works on OSGi distributions based on Apache Felix such as Apache Sling, Apache Karaf, Apache ServiceMix etc.
- searching for bundles, services, configurations and classes (with wildcard support),
- searching in decompiled classes sources that come from selected elements (e.g multiple bundles),
- generating ZIP file with all:
- decompiled class sources from selected elements (e.g multiple bundles),
- bundle JAR's related with selected elements
- bundle class tree view with jumping between decompiled class sources,
- one-click bundle JAR download.
You liked plugin? Please don't forget to star this project on GitHub :)
Manually install ready to use bundle search-webconsole-plugin-x.x.x.jar using web console interface.
Build and deploy automatically using command: mvn clean package sling:install
.
Do not hesistate to fork and create pull requests.
If your container is available on different URL than http://localhost:8181/system/console, just override properties in following way:
mvn clean install sling:install -Dfelix.url=http://localhost:8080/felix/console -Dfelix.user=foo -Dfelix.password=bar
On pure Felix distribution, for instance com.sun.*
package is not available by default, but it is required by decompiler to work.
To fix that problem just include packages within boot delegation in a same way as Karaf does in config.properties:
org.osgi.framework.bootdelegation = \
com.sun.*, \
sun.*
Also, by default, bundle storage directory is not specified in Felix distribution.
Plugin assumes that if property org.osgi.framework.storage
is not defined, directory ./felix-cache will be used instead.
Plugin is published on BinTray: https://bintray.com/neva-dev/maven-public/felix-search-webconsole-plugin.
Search Web Console Plugin is licensed under Apache License, Version 2.0 (the "License")
Any usage of that tool and legal consequences must be considered as done at own risk. For instance, decompiled source code can be protected by copyrights and author does not take any responsibility for such usages.
Using that tool is absolutely optional. Original purpose of usage of built-in decompiler is to quickly view class sources used at runtime that are even available in public Internet, so that code debugging can take less time.