The deployment packaging does not have to be tied to the release cycle /
code management.
Think about the simple use case where you implement a public interface: you
don't release the API (it may never change), but you're still free to embed
the API in your bundle or not.
Also, the use case for
Hi,
I think it's better to separate bundle interface and bundle
implementation, you can have many implementations of the same interface
(like OSGi specifications) and you can release a new implementation
version without release the api version. Generally, implementations
bundles are releases more
Why do you advise that fat bundles should be avoided? My current idea of good
osgi design is to only export service interfaces, and generally package the
interfaces with the implementations; since jarA and libA aren’t even bundles
they are good candidates for hiding inside bundleA since they
One more thing that might be helpful, my bitvise client reconnects... so
there is a set of logs where it's been connecting and getting disconnected,
looks like it's happening every 10 minutes, I wasn't doing anything with
Karaf during that time:
18:25:48.014 WARN
Hi Alex,
1) I guess your are using the OSGi HTTP service (so Pax Web). Then you can use
the Jetty NCSARequestLog (globally or per application). Karaf provides security
audit log.
2) Decanter can help you there: it can harvest all MBeans metrics (via the JMX
Collector). You can then check
It seems you embed lot of packages in your bundle, which is wrong generally
speaking.
I would advice to correctly import the packages.
Regards
JB
On 01/04/2018 07:09 PM, GFO wrote:
Hi,
I think it has been deleted, it was in the message when I previewed it...
Here is the pastebin link:
Greetings Karaf community.
Two questions:
1) I understand that Karaf can be used to host lots of different things,
however things that are used to serve up HTTP requests, is there any built
in mechanism for audit the message traffic for these HTTP requests (or any
other protocol for that
Do you embedded a Spring dependencie in your bundle ?
Le 4 janv. 2018 10:09 PM, GFO a écrit : > > Hi, > > I think it has been
deleted, it was in the message when I previewed it... > > Here is the pastebin
link: https://pastebin.com/LkKDwv89 > > Thanks, > GFO > > > > -- > Sent from:
Hi,
I think it has been deleted, it was in the message when I previewed it...
Here is the pastebin link: https://pastebin.com/LkKDwv89
Thanks,
GFO
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Hi,
You forgot to paste your error stack trace ;)
François
Le 04/01/2018 à 21:48, GFO a écrit :
> Hi,
>
> I am trying to launch my bundle.
>
> However, I have the following error:
>
>
>
> Here is my camel-context.xml file: https://pastebin.com/CsxSDZsv
>
> I know this error can come from
Hi,
I am trying to launch my bundle.
However, I have the following error:
Here is my camel-context.xml file: https://pastebin.com/CsxSDZsv
I know this error can come from namespaces in my file. I tried several
things:
- remove the version number in XSD spring links
- change the version
Did you check your import/export ?
Creating a uber bundle is also an option, but fat bundles should be avoided.
Regards
JB
On 01/04/2018 06:18 PM, GFO wrote:
Hi,
Thanks for your answer.
I have tried to create a kar file: my bundle does not find some dependencies
although dependencies are
Hi,
Thanks for your answer.
I have tried to create a kar file: my bundle does not find some dependencies
although dependencies are started as bundles.
I have the following dependencies:
BundleA (mine) depends on jarA (mine) which depends on libA (third party).
jarA and libA are wrapped as
Thanks for the update.
Let me try to reproduce this behavior.
Regards
JB
On 01/04/2018 04:56 PM, Ryan Moquin wrote:
Yes, sorry, 4.0.12. Yes, with both the Karaf client and an OpenSSH client I see
this happen. Let me just re-verify that if I start up karaf with absolutely
nothing in it and
Yes, sorry, 4.0.12. Yes, with both the Karaf client and an OpenSSH client
I see this happen. Let me just re-verify that if I start up karaf with
absolutely nothing in it and ssh to it locally that it times out. Want to
make sure no bundles are clobbering anything. The logging gets messed up
Hi Ryan,
Are you using the Karaf client or OpenSSH client ?
You just type log:tail ?
I didn't notice such timeout.
By the way, I guess you mean Karaf 4.0.12 (not 4.1.12) right ?
Regards
JB
On 01/04/2018 04:34 PM, Ryan Moquin wrote:
Out of curiosity, since this is driving me a bit batty
Out of curiosity, since this is driving me a bit batty because I usually
SSH into Karaf locally to tail the log, is there a bug in the SSH library
that Karaf uses to provide SSH access? The past few releases of Karaf,
4.1.13, 4.1.14 and 4.2.0 all timeout after a few minutes of being connected
via
Hi,
1/ If you really want a zip file, then take a kar.
If you want to work with a repo, feature is better.
2/ It's possible using fileinstall and specifying your folder
3/ Cave can be an option too (with Bundle Repository).
Regards
JB
On 01/04/2018 12:05 PM, GFO wrote:
Hello,
I have a
Hello,
I have a question about dependencies in Karaf.
I have a bundle which contains a lot of dependencies:
- jars created by me
- third party jars
Those dependencies may have transitive dependencies.
To deploy my application in a production environment I would like a zip file
19 matches
Mail list logo
