Hi Andrei, You could add a new log appender (JMS, ....) as a bundle. This appender should implements the interface PaxAppender of Pax Logging and registers a service. I have created yesterday a JMS Appender for ActiveMQ that we will use on ServiceMix. Depending when you have to use it or not, you could stop / start the bundle exposing a Pax Loggin OSGI Service. Another solution is maybe to use the camel paxlogging component ( http://camel.apache.org/pax-logging.html) in combination with your camel-aws and a trigger pattern to decide when you must send or not / log or not.
Regards, Charles Moulliard Apache Committer / Sr. Pr. Consultant at FuseSource.com Twitter : @cmoulliard Blog : http://cmoulliard.blogspot.com On Thu, Aug 9, 2012 at 5:59 AM, Andrei Pozolotin <[email protected] > wrote: > *Hi;* > > I am curious what is the right way to > > add new log appender dynamically to org.ops4j.pax.logging at run time > > that is, NOT programmatically, but from a sibling config file such as > ${karaf.base}/etc/org.ops4j.pax.logging-extra.cfg > > ? > > I can not find this feature in the source, must be looking in the wrong > place :-) > > use case: AWS SNS based appender should be activated/deactivated on demand; > http://aws.amazon.com/sns/ > > Thank you, > > Andrei > >
