JB:
Original Message
Subject: Re: update snapshot dependency?
From: Jean-Baptiste Onofré
To: Andrei Pozolotin
Cc: user@karaf.apache.org
Date: Tue 12 Feb 2013 12:17:52 AM CST
> Hi,
>
> we already have bundle:update.
bundle:update does not fetch new snapshot for me
what am I miss
Yes, that is how its working, thanks for the confirmation.
I was under the impression that it will merge the multiple configurations
and build a effective configuration.
--
View this message in context:
http://karaf.922171.n3.nabble.com/Jetty-fragment-bundle-is-not-considered-by-pax-web-tp
thank you!
Original Message
Subject: Re: KARAF-2180 : feature update failure
From: Jean-Baptiste Onofré
To: user@karaf.apache.org
Date: Tue 12 Feb 2013 09:16:25 AM CST
> Hi Andrei,
>
> I gonna try to reproduce.
>
> I guess that you mean put features.xml in deploy (not in etc), r
Hi Andrei,
I gonna try to reproduce.
I guess that you mean put features.xml in deploy (not in etc), right ?
Regards
JB
On 02/12/2013 04:13 PM, Andrei Pozolotin wrote:
*Hello*
I am curious if others see this
https://issues.apache.org/jira/browse/KARAF-2180
and what is the wor
*Hello*
I am curious if others see this
https://issues.apache.org/jira/browse/KARAF-2180
and what is the work around?
Thank you,
Andrei
Hi the answer is quite simple, if Pax-Web finds a jetty.xml at the
configured file location it uses that one opposed to the fragment. If you
don't want to use it you need to configure Pax-Web to not look for it.
After that you should be able to use your fragment.
Though why don't you use the alrea
Hi,
I am using Karaf 2.3.0.
I am creating a fragment bundle for adding JAAS login service to jetty. But
looks like it is not considered and I am netting login service not foud
exception. If add same to the etc/jetty.xml then it works fine. What could
be the issue ?
'Fragment-Host': org.ops4j.pax
Hi Graham,
RMI registry (1099) and RMI server (4) are used by the JMX layer.
You can configure it in etc/org.apache.karaf.management.cfg.
Another port by default is 8101 (used by the SSH layer) that you can
configure in etc/org.apache.karaf.shell.cfg.
I did the same as you (using netsta
Hi all,
I am currently trying to security harden the default version of karaf. When the
default latest version of v2.3.0 is started up with a default configuration, it
binds to and listens on the following ports:
[minfrin@localhost bin]$ lsof -p 11151 | grep LISTEN
java11151 minfrin 15u
