ok thanks a lot Timothy and all the guys that's nice from you :)
2017-02-15 15:17 GMT+01:00 Timothy Ward :
> The way that you deploy a bundle is heavily dependent on the management
> agent that you choose to use.
>
> The bnd “export” is a simple management agent used to
The way that you deploy a bundle is heavily dependent on the management agent
that you choose to use.
The bnd “export” is a simple management agent used to package up a bunch of
bundles with a framework into a runnable jar file.
If you want to deploy the individual bundles into another
Hey Raymond, that's what I'm trying to do actually yup!
So it looks that it's not the way..
How could I deploy a bundle into an osgi container ??
2017-02-15 15:01 GMT+01:00 Raymond Auge :
> Are you perhaps trying to install the jar created by the bndtools "export"
>
Are you perhaps trying to install the jar created by the bndtools "export"
process into concierge?
The jar created by export is executable. Just run it as:
java -jar exported.jar
Just a thought,
- Ray
On Feb 15, 2017 04:30, "Dirk Fauth" wrote:
> Hard to tell. But you
Hard to tell. But you say you run on a Java 8 compact 1 and specify a
requirement to Java 8 only. Not sure how the runtime treats that. I think
you should explicitly require compact1 if you intend to run on that.
Am 15.02.2017 9:29 AM schrieb "Mestiri Meher" :
Hello,
I
Hello,
I want to thank you for your help, it's really nice to see a community
helping on osgi.
So here's the manifest generated:
Manifest-Version: 1.0
Bnd-LastModified: 1487091798569
Bundle-Description: A bundle with a provider. Notice that this provide
r exports the API package. It also
How did you create the bundles? Do you use Bndtools or Eclipse PDE?
The export section of the manifest would be interesting to see.
Am 14.02.2017 6:15 PM schrieb "Neil Bartlett" :
> The inspect command has the wrong parameters. It should be:
>
> inspect
The inspect command has the wrong parameters. It should be:
inspect capability|requirement
Note that capability and requirement can be abbreviated to just “c” and “r”.
I think what you’re trying to do is view the exports of bundle 13, like this:
inspect c osgi.wiring.package
>From the BundleException that you posted above, it looks like you're
deploying an OSGi R3 bundle, which might indicate that your bundle manifest
is incorrect or incomplete. You should really be deploying OSGi R4 or later
bundles.
Make sure the following manifest headers are present in your jar's
I triedd this command too : "inspect capability 13"
and here what I got:
org.apache.felix.framework [0] provides:
13 [EMPTY]
2017-02-14 16:55 GMT+01:00 Mestiri Meher :
> Hey thanks Dirk for your answer,
>
> Actually it's only
Did you check if all bundles are started that you need? Execute lb in the
console to get the list of installed bundles and their states.
Am 14.02.2017 4:41 PM schrieb "Mestiri Meher" :
Hello guys,
I'm new to the OSGI and I'm trying to learn it from the OSGI enRoute
Hey thanks Dirk for your answer,
Actually it's only jar : the provider one for the first example and once I
tried deploying the api project it says
: org.osgi.framework.BundleException: R3 exports cannot contain directives.
Otherwise all the felix bundles are working :
ID|State
Hello guys,
I'm new to the OSGI and I'm trying to learn it from the OSGI enRoute
tutorials.
I build the API/Provider, it runs on eclipse with felix gogo and the
commands run fine.
I tried exporting my jar and deploy it manually on concierge/felix
standalone I was able to start the bundle on
13 matches
Mail list logo