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 framework that you’re starting some other way then you will need to use something like Felix File Install, the Felix Gogo shell, or some other framework dependent mechanism to install/start the bundles. Regards, Tim > On 15 Feb 2017, at 14:09, Mestiri Meher <meher.mest...@gmail.com> wrote: > > 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 <raymond.a...@liferay.com > <mailto:raymond.a...@liferay.com>>: > 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" <dirk.fa...@gmail.com > <mailto:dirk.fa...@gmail.com>> wrote: > 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" <meher.mest...@gmail.com > <mailto:meher.mest...@gmail.com>>: > 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 provides a JUnit test and it can b > e run standalone. > Bundle-ManifestVersion: 2 > Bundle-Name: com.lm.meher.provider > Bundle-SymbolicName: com.lm.meher.provider > Bundle-Version: 1.0.0.201702141703 > Created-By: 1.8.0_121 (Oracle Corporation) > Export-Package: com.lm.meher.api;version="1.0.0" > Import-Package: com.lm.meher.api;version="[1.0,2)" > Private-Package: com.lm.meher.provider > Provide-Capability: osgi.service;objectClass:List<String>="com.lm.mehe > r.api.Meher" > Require-Capability: osgi.ee <http://osgi.ee/>;filter:="(&(osgi.ee > <http://osgi.ee/>=JavaSE)(version=1.8))" > Service-Component: OSGI-INF/com.lm.meher.xml > Tool: Bnd-3.3.0.201609221906 > > Dirk, as you see I'm using the version2. > > The bundles I created them using the enRoute framework that is using the > bndtools normally. > It's a tutorial that i found in here: > http://enroute.osgi.org/tutorial_base/050-start.html > <http://enroute.osgi.org/tutorial_base/050-start.html> > > I think my issue is that I'm following the tutorial, so I have these 2 > parameters in my .bnd file: > > -runfw: > org.eclipse.osgi;version='[3.10.100.v20150529-1857,3.10.100.v20150529-1857]' > -runee: JavaSE-1.8 > > And I'm trying to deploy that jar into felix/concierge under a java se > embedded compact1. > Of course under these 2 containers, I was able to manage the lifecycle of the > bundle, but never execute the commands I created. > > > 2017-02-14 18:43 GMT+01:00 Dirk Fauth <dirk.fa...@gmail.com > <mailto:dirk.fa...@gmail.com>>: > 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" <njbartl...@gmail.com > <mailto:njbartl...@gmail.com>>: > The inspect command has the wrong parameters. It should be: > > inspect capability|requirement <namespace> <bundles> > > 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 13 > > Regards, > Neil > >> On 14 Feb 2017, at 15:59, Mestiri Meher <meher.mest...@gmail.com >> <mailto:meher.mest...@gmail.com>> wrote: >> >> 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 <meher.mest...@gmail.com >> <mailto:meher.mest...@gmail.com>>: >> 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 |Level|Name >> 0|Active | 0|System Bundle (5.6.1)|5.6.1 >> 1|Active | 1|Apache Felix Bundle Repository (2.0.8)|2.0.8 >> 2|Active | 1|Apache Felix Gogo Command (0.16.0)|0.16.0 >> 3|Active | 1|Apache Felix Gogo Runtime (0.16.2)|0.16.2 >> 4|Active | 1|Apache Felix Gogo Shell (0.10.0)|0.10.0 >> >> >> >> >> 2017-02-14 16:49 GMT+01:00 Dirk Fauth <dirk.fa...@gmail.com >> <mailto:dirk.fa...@gmail.com>>: >> 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" <meher.mest...@gmail.com >> <mailto:meher.mest...@gmail.com>>: >> 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 both of containers, and manage >> them. >> >> The problem is that I can not see the commands I declared in the provider. >> Once I type the help gogo command, I can't see my commands in there, but in >> eclipse the gogo command are prresent. >> >> I don't know how to figure this out, it says gogo commandNotFoundException. >> >> Do you have an idea ? >> >> Thanks, >> Meher >> >> _______________________________________________ >> OSGi Developer Mail List >> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> <https://mail.osgi.org/mailman/listinfo/osgi-dev> >> >> >> _______________________________________________ >> OSGi Developer Mail List >> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> <https://mail.osgi.org/mailman/listinfo/osgi-dev> >> >> >> _______________________________________________ >> OSGi Developer Mail List >> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> <https://mail.osgi.org/mailman/listinfo/osgi-dev> > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> > https://mail.osgi.org/mailman/listinfo/osgi-dev > <https://mail.osgi.org/mailman/listinfo/osgi-dev> > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> > https://mail.osgi.org/mailman/listinfo/osgi-dev > <https://mail.osgi.org/mailman/listinfo/osgi-dev> > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> > https://mail.osgi.org/mailman/listinfo/osgi-dev > <https://mail.osgi.org/mailman/listinfo/osgi-dev> > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> > https://mail.osgi.org/mailman/listinfo/osgi-dev > <https://mail.osgi.org/mailman/listinfo/osgi-dev> > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> > https://mail.osgi.org/mailman/listinfo/osgi-dev > <https://mail.osgi.org/mailman/listinfo/osgi-dev> > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
