I've been working with Karaf and features a lot recently. I was curious how a webconsole plugin would work so I looked at your code. I was happy to see that things seemed very simple and straight-forward so I was inspired to try to extend your features plugin.
I quickly discovered that things are not what they appeared. I didn't investigate how the core plugins are loaded but the features plugin appears to be loaded via Spring. Loading plugins this way doesn't use AbstractWebConsolePlugin as it is "advertised" and many things just don't work (activate() and deactivate() are never called, getBundleContext() returns null, etc). It looks like a lot of the webconsole infrastructure is hidden in org.apache.felix.webconsole.internal so to get a plugin working with any reasonable functionality would require duplicating a lot of those classes. Perhaps I missed the proper way to initialize a webconsole plugin and get at the utility methods. If not, I would suggest refactoring the infrastructure of webconsole so that extending AbstractWebConsolePlugin does work as expected. Tim Moloney The reasonable man adapts himself to MRSL the world; the unreasonable one persists 2015 Cattlemen Road in trying to adapt the world to himself. Sarasota, FL 34232 Therefore all progress depends on the (941) 377-6775 x208 unreasonable man. George Bernard Shaw > -----Original Message----- > From: Marcin Wilkos [mailto:marcin.wil...@gmail.com] > Sent: Monday, June 08, 2009 17:32 > To: dev@felix.apache.org > Subject: Google Summer of Code > > Hi, > I'm Marcin Wilkos. Like Gert Vanthienen wrote before I'm working on > webconsole for Karaf and ServiceMix as GSoC project. I'll be > sending weekly > reports to this list. > In last week I focused on first extension for felix web > console, which lists > Karaf features. I created JIRA issue for this and uploaded a > patch. Gert > checked it and uploaded to svn. > Regards, > Marcin Wilkos >
