Hi, hmm, ok. In this case we really have to crosscheck the metatype.xml files, which have been handcrafted so far.
Regards Felix Am 06.10.2011 um 23:15 schrieb Justin Edelson: > On Thu, Oct 6, 2011 at 5:04 PM, Felix Meschberger <[email protected]> wrote: >> Hi, >> >> On 06.10.2011 22:51, Justin Edelson wrote: >>> I'm not sure if this has always been the case (and I am just noticing >>> it now) or it started happening recently, but I noticed that there are >>> two more lines in the Configurations web console plugin for logging >>> than I would expect. >>> >>> I see these options: >>> Apache Sling Logging Configuration (non-factory) >> This is correct; since this is plain, non-factory config. > > Right. I expect this line. It's the other non-factory lines I don't expect. > >>> Apache Sling Logging Logger Configuration (non-factory) >>> Apache Sling Logging Logger Configuration (factory) >>> Apache Sling Logging Writer Configuration (non-factory) >>> Apache Sling Logging Writer Configuration (factory) >> I would consider this a bug in the Web Console, which does too much here. > > Really? Because this isn't an issue with other factory configurations > (e.g. org.apache.sling.engine.impl.log.RequestLoggerService, > org.apache.sling.jcr.jackrabbit.server.SlingServerRepository, and > org.apache.sling.fsprovider.internal.FsResourceProvider all show up > correctly). > > Justin > >> >> Regards >> Felix >>> Apache Sling Logging Logger Configuration (non-factory) and Apache >>> Sling Logging Writer Configuration (non-factory) don't seem to have >>> corresponding ManagedService services. At least for the latter, >>> creating a configuration with that PID doesn't seem to invoke any >>> code. >>> >>> Is this a typo in the metatype.xml? Or I missing some purpose behind >>> these entries? >>> >>> screenshot here: http://screencast.com/t/xafmWeatwt >>> >>> Thanks, >>> Justin >>> >> >>
