Hi,
It's simply a ManagedServiceFactory via SCR.
The factory is org.apache.karaf.decanter.jmx.
So, as soon as you create a config org.apache.karaf.decanter.jmx-foo
a new service is created associated with this configuration.
Regards
JB
On 21/06/2019 08:46, Oliver Wulff wrote:
> Hi there
>
>
Hi JB,
Could you show me where I could add the filter properties as you mentioned
or if it’s not implemented yet, some guidance on accessing the appender or
Marshaller properties file from inside the default decanter json appender?
Thanks
On Wed, 12 Jun 2019 at 11:53 am, Noobtube Account
wro
Hi,
I guess you are talking about filtering of the events to send to the
appender right ?
I will update the Decanter documentation with some example and how it works.
In the mean time, you can take a look on the test illustrating the
events filtering:
https://github.com/apache/karaf-decanter/bl
Yes, it's an impressive accomplishment, I hope I didn't come off the wrong
way with my questions. I wanted to figure out how the JAX-RS whiteboard
stuff might play together with the CXF REST services I already have. I'll
make sure to ask any further questions in the Aries list.
Ryan
On Wed, Jun
For the realm, I'm using an arbitrary string. Is there a specific realm I
should be using? That whole realm thing confuses me a bit, I'm unclear as to
how it's used.
Scott
From: Francois Papon
Sent: Thursday, June 20, 2019 11:04 PM
To: user@karaf.apache.org
Subject: Re: Karaf 4.2.5 Jetty cli
Felix SCR doesn’t use ManagedServiceFactory to implement support for factory
configurations (I don’t think it’s actually possible), so what your description
literally can only mean is that you have a DS component implementing
ManagedServiceFactory. This is possible but rather unusual. I rather s
You are right David (even a little rude, whatever), my wording was not
accurate.
I tried to mean that we are using factory SIMILAR (but not the same as)
to ManagedFactory.
Regards
JB
On 21/06/2019 17:40, David Jencks wrote:
> Felix SCR doesn’t use ManagedServiceFactory to implement support for f
> cooshal :
> Hi:
> thank you !
> I will look at it and will get back to you.
> When I started this project, I used a very simple approach, which did not
> require any involvement of web.xml configuration. Later, I realized that I
> chose the wrong architecture.
> I will try and test with y
Just FYI: ECF's impl of OSGi R7 Remote Services has a CXF [1] as Karaf
features.
This uses only Jax-RS 2 annotations rather than the OSGI annotations,
and since OSGi spec'd works seamlessly with DS.
There's a tutorial here [2] that uses either Jersey or CXF. Of course
any existing servic
Hi JB,
Found a particular bundle that is getting start when installing kar with
only 1 feature with 1 bundle:
The org.hamcrest.core is always trying to start regardless of no start
option. Here is my feature xml:
mvn:org.hamcrest/core/1.3.0-v201303031735
Here is console log show t
Hello,
I'm using karaf 4.2.6 to host a simple web bundle, the bundle is installed,
ServletContextHelper, resource service started but i cannot access any
resource, the web console show my servlet deployed to the wrong context.
Here is the output from the karaf console:
karaf@root()> bundle:list -
Hi,
Same context when you do http:list ?
Regards
JB
On 21/06/2019 23:49, ntle wrote:
> Hello,
>
> I'm using karaf 4.2.6 to host a simple web bundle, the bundle is installed,
> ServletContextHelper, resource service started but i cannot access any
> resource, the web console show my servlet depl
By the way, I think you can workaround adding alias service property.
Regards
JB
On 21/06/2019 23:49, ntle wrote:
> Hello,
>
> I'm using karaf 4.2.6 to host a simple web bundle, the bundle is installed,
> ServletContextHelper, resource service started but i cannot access any
> resource, the web
13 matches
Mail list logo
