Sure.
The whole thread had started based on an attempt done to use log4j flume
appender with Karaf. Unfortunately it didn't work for me .While I tried
the logback flume appender it worked without any issues till I hit this
issue of setting/getting of log-levels. I can switch back to log4j - if
Hi,
ok, ah it's because of the flume appender.
Maybe I've some cycles to take a look at it later.
regards, Achim
2014-11-13 8:58 GMT+01:00 syedbahm :
> Sure.
>
> The whole thread had started based on an attempt done to use log4j flume
> appender with Karaf. Unfortunately it didn't work for me
Hi
I'd like to know which is the better way to have some dependency between
2 bundles so that a bundle will not start before its dependency is in an
active state ?
Thanks for answers
Mat
Using start levels isn't sufficient?
But what is the reason for wanting/needing the dependency? Understanding
the root issue may help identify a better solution.
On Thu, Nov 13, 2014 at 9:39 AM, Matthieu Vincent
wrote:
> Hi
>
> I'd like to know which is the better way to have some dependency
Hi Matthieu,
you can use start-level, but honestly, I would recommend to use features.
Let say, you have bundle1 and bundle2, where bundle2 depends to bundle1.
You can define:
.../bundle1
feature1
../bundle2
Regards
JB
On 11/13/2014 06:39 PM, Matthieu Vincent wrote:
Hi
I'd like to
Hi all
My problem is thar i've got a bundle starting consumer en JMS queues that
must wait for my business bundle to start which can be "long" so i need the
first one to wait thé second.
Features and start level didn't fix my problem. I've already tried.
Mat
Le 13 nov. 2014 19:34, "Jean-Baptiste
Hi,
maybe you can manage using the Activator to check the state of the
service or other bundle.
Can you describe a bit what you use (blueprint, DS, etc) ?
Regards
JB
On 11/13/2014 07:50 PM, Matthieu Vincent wrote:
Hi all
My problem is thar i've got a bundle starting consumer en JMS queues
Hi
I was thinking about using either activator or tracker.
But in both cases, if business service is unavailable the bundle will go in
failure. So I need to use some monitoring to restart bundle after a while.
Other option can be a kind of while loop to wait fort service but i dont
really like th
Hi,
if you use a service tracker you don't need a while loop, cause it will
"active" in the second the service is available.
Best to do that without blueprint, blueprint does have a graceperiod. Maybe
DS is more suitable for this.
regards, Achim
2014-11-13 21:20 GMT+01:00 Matthieu Vincent :
> H
Hi Achim
Can u tell me more about your DS idea ?
Thanks
Le 13 nov. 2014 21:32, "Achim Nierbeck" a écrit :
> Hi,
>
> if you use a service tracker you don't need a while loop, cause it will
> "active" in the second the service is available.
> Best to do that without blueprint, blueprint does have
Hi Matthieu,
for Declarative Services (DS) you might want to take a look at [1].
It's basically a "Boilerplate code free" ServiceTracking :)
regards, Achim
[1] - http://wiki.osgi.org/wiki/Declarative_Services
2014-11-13 22:18 GMT+01:00 Matthieu Vincent :
> Hi Achim
>
> Can u tell me more abou
Hi,
in Karaf 3.0.x, install the service-wrapper feature with:
feature:install wrapper
(earlier, the command was features:install ...). Then activate the wrapper
with:
wrapper:install -s AUTO_START –n -d
-D
ln -s /bin/KARAF-service /etc/init.d/
update-rc.d KARAF-service defaults; # for Debia
12 matches
Mail list logo