I did some experement.
Glassfish 4 and Karaf 3.0.2 have the same felix version 4.2.1. Bundles in
glassfish works fine after crash. I moved felix.jar from glassfish to karaf,
Karaf still wont resolving bundles which installed before crash. Glassfish
3.1.2.2 has felix 4.0.2. I moved felix.jar
Did you try on Karaf using Equinox ?
As I said in my previous e-mail, we directly leverage the framework for
bundle management. Anyway, I re-open the Jira about this to double check.
Regards
JB
On 12/10/2014 10:04 AM, Bellski wrote:
I did some experement.
Glassfish 4 and Karaf 3.0.2 have
jbonofre wrote
Did you try on Karaf using Equinox ?
As I said in my previous e-mail, we directly leverage the framework for
bundle management. Anyway, I re-open the Jira about this to double check.
Yes, it works with strange, but it works. I wrote in another mail about
permanent Karaf
Thanks for the update.
I'm testing on 4.0.0-SNAPSHOT right now, I will send to you an update in
10mn or so.
Regards
JB
On 12/10/2014 10:21 AM, Bellski wrote:
jbonofre wrote
Did you try on Karaf using Equinox ?
As I said in my previous e-mail, we directly leverage the framework for
bundle
This is the test that I did on Karaf 4.0.0-SNAPSHOT, Felix framework
4.4.1, Oracle JDK 1.7, Linux:
0/ I start karaf with bin/karaf
1/ I installed the war feature:
karaf@root() feature:install war
2/ I installed and started a bundle:
karaf@root() bundle:install
Gimme time. I'll all tests
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-4-0-0M1-wont-resolve-random-bundles-after-crush-tp4036956p4037104.html
Sent from the Karaf - User mailing list archive at Nabble.com.
You absolutely right. I think it's problem in first configuration from my
plugin. Any way why it works on all versions of Glassfish and Equinox :/ Sry
for wasting your time.
--
View this message in context:
4.0.0M1 wont resolve random bundles after crush
You absolutely right. I think it's problem in first configuration from my
plugin. Any way why it works on all versions of Glassfish and Equinox :/ Sry
for wasting your time.
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf
jbonofre wrote
Thanks again for the update.
Can you share what you found about your plugin configuration as it can be
helpful for other users ?
Regarding obr yes: in your features XML, on a
feature/
element you can define resolver=obr. If the obr feature is installed
and you have obr
which right ?
?xml version=1.0 encoding=UTF-8 standalone=yes?
features xmlns=http://karaf.apache.org/xmlns/features/v1.3.0;
name=cas2-1.0.0
feature name=cas2 description=cas2 version=1.0.0
*resolverobr/resolver*
detailscas2/details
bundle
features ...
feature name=my description=foo version=x.x.x resolver=(obr)
/feature
/features
Regards
JB
On 12/10/2014 04:07 PM, Bellski wrote:
which right ?
?xml version=1.0 encoding=UTF-8 standalone=yes?
features xmlns=http://karaf.apache.org/xmlns/features/v1.3.0;
Hello. I have two problems which stops our company migrate to the Karaf.
*Karaf version:* 4.0.0.0M1
*OS:* Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
*JVM:* 1.7 latest
1. If deploy bundle from file system or from obr , then kill karaf without
normal shutdown and start. Karaf will
Hi,
See my comments inline:
*Karaf version:* 4.0.0.0M1
*OS:* Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
*JVM:* 1.7 latest
1. If deploy bundle from file system or from obr , then kill karaf without
normal shutdown and start. Karaf will not resolve/start this bundle or
bundles.
jbonofre wrote
Do you use Felix as framework ?
Yeap. By karaf default
jbonofre wrote
Unfortunately, the bundle cache of the framework get corrupted (it's not
directly a Karaf bug, but more a framework bug).
We're using Glassfish. Glassfish uses Felix and we never had problems with
Regarding Glassfish, the Felix version is the same as in Karaf 2.1: yes
Glassfish uses a very old Felix version.
So you can make a try with Karaf 2.3.x, I'm pretty sure that you won't
see the problem. It seems that we encounter this problem since Felix 4.x.
Regards
JB
On 12/04/2014 10:35
jbonofre wrote
Regarding Glassfish, the Felix version is the same as in Karaf 2.1: yes
Glassfish uses a very old Felix version.
So you can make a try with Karaf 2.3.x, I'm pretty sure that you won't
see the problem. It seems that we encounter this problem since Felix 4.x.
Good new ;) I
Just wanted to chime in regarding the comment about the enterprise
stability of Karaf. I wanted to note that it wouldn't be fair to draw
stability conclusions of Karaf based on a milestone version of Karaf. If
you will be putting this in production in the short term, you might want to
use a
Hi,
websockets should also work nicely with Karaf 3.x due to Jetty 8.
It supported websockets already, you just need to make sure to have the
right websocket servlet registered.
If you look for a the latest JSR-356 implementation this will only work
with Pax Web 4.1 which isn't connected to Karaf
18 matches
Mail list logo
