your site seems to have gone sideways. On Fri, Aug 21, 2015 at 7:14 PM, Christian Schneider < [email protected]> wrote:
> Hi Benson, > > not exactly with config admin but there is a good solution. > > See my article about the new CXF logging feature: > http://www.liquid-reality.de/x/AoDT > > So basically you simply start the logging feature before your first bundle > using cxf is started and it will enhance all cxf clients and servers with > logging. > The logs by default got to slf4j. Each service has its own logger name. So > you can use the pax logging config to define which service should be > logged. When a service is switched off this way there is almost no > performance impact from the logging feature. > > Additionally like described in the article you can easily feed the service > logs into Decanter so they end up in elastic search and can be nicely > searched and visualized. > > Christian > > > Am 21.08.2015 um 23:32 schrieb Benson Margulies: > >> While I know that blueprint has a bad odor, I am working with a very >> simple device that does not get into any of the problems with service >> dependencies (as far as I can tell). >> >> I currently have: >> >> <cxf:bus> >> <cxf:features> >> <!-- >> <cxf:logging/> >> --> >> </cxf:features> >> </cxf:bus> >> >> because I realized, belatedly, that I'd invited someone to do a >> performance test with logging turned on. Having to edit blueprint.xml >> to turn it on and off is not delux, it seems like the sort of thing >> that config admin was intended to do. >> > >
