Re: Caused by: java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory not found by org.apache.karaf.webconsole.console [73]

2019-07-10 Thread Владимир Коньков
Hello! See https://github.com/eclipse-ee4j/jaxb-api/issues/78 You can build your own version of jaxb-api and replace it in $karaf_home/lib/jdk9plus . Or wait official release of JAXB-API and dependency upgrade in Karaf. Once JAXB-API is

Proposal: ability to install features in different regions in single command

2016-03-23 Thread Владимир Коньков
Hi there! Use case: Environment: clean Karaf 4.x instance. Requirements: Multiple software modules should be install according to accepted deployment plan. Deployment plan consist 3 modules in different regions: ActiveMQ (root/broker), business module A (root), business module B (root). Some

Re: Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default

2016-03-21 Thread Владимир Коньков
;a simple way" to provide/add it (not necessary a Karaf > feature) ;) > > Probably the easier way now is to document how to do it in the dev guide with > an associated sample. > > Regards > JB > > On 03/19/2016 03:03 PM, Владимир Коньков wrote: >> Hi Jean-

Re: Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default

2016-03-19 Thread Владимир Коньков
Hi there! Lukasz, Jean-Baptiste, thanx for reply. Actually your opinion is expected and reasonable. Lukasz, couple of comments: Proposed solution is not specific for any tool - GELF is very common format for app log streaming and it’s popularity is growing. About custom distribution:

Re: Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default

2016-03-19 Thread Владимир Коньков
n propose > an optional feature to add this. > > WDYT ? > > Regards > JB > > On 03/17/2016 06:33 AM, Владимир Коньков wrote: >> Hi there! >> >> Lukasz, Jean-Baptiste, thanx for reply. Actually your opinion is expected >> and reasonable. >>

Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default

2016-03-16 Thread Владимир Коньков
Hi As of version 4.1 Karaf will use Log4J 2 as logging backend (thanx, Guillaume). It’s very good news, because it greatly simplify configuration of robust production logging - compression, flexible rotation rules, async, fallback logging. All this features comes out of the box with Log4J 2.