The logging support in Virgo is great. I have found that the application-specific logging works for pars but does not work for single bundles. Bundle output gets written to virgo-server/log.log but not its own application-specific log. Is there a way to make that happen? Is there a good reason that I shouldn't want/need that to happen?
The difficulty is knowing the boundary of the application. For PARs, scoped plans, and web applications, there is some sort of boundary of the application. For bundles it's far from clear.
I can certainly see your desire to have application trace for single bundle applications though, so you may like to raise an enhancement bugzilla. One solution would be to define a custom manifest header to trigger this, although I haven't given it much thought yet to be sure of feasibility. But note that it would be hard to use this technique to make an app consisting of multiple bundles using a single application log, unless we also defined an application name in the manifest header (independently of the bundle symbolic name).
Thanks for the input on this. After working more with OSGi and Virgo, I'm seeing that logging a single bundle is not as useful as I once thought it was. Plans are great and almost all scenarios in which I'd want a log are now using plans. If I really need to log a single bundle, I can create a plan for it, but really it would make me reconsider my bundle design... If a bundle is doing enough work to need logging, it can probably be split up in to separate bundles that each do less. That's what OSGi is all about, right?