Databases
StackOverflow2013
Postsdbo
POExporting a bundle with dependencies with another bundles
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POExporting a bundle with dependencies with another bundles
    primarykey
    data
    text
    <p>I have this OSGI configuration:</p> <pre><code>/configurations config.ini somebundle.properties /plugins bundleA bundleB osgi-3.4.2-R34x_v2008826-1230.jar org.eclipse.equinox.common_3.4.0.v20080421-2006.jar org.eclipse.update.configurator_3.2.201.R34x_v20080819.jar com.test.arquitectura.osgi.ConfiguratorModule_1.0.0.jar </code></pre> <p>My config.ini is like this:</p> <pre><code>osgi.bundles=org.eclipse.equinox.common@2:start, \ org.eclipse.update.configurator@3:start, \ com.test.arquitectura.osgi.ConfiguratorModule_1.0.0.jar@3:start osgi.clean = true eclipse.ignoreApp=true osgi.parentClassLoader=app </code></pre> <p>So, AFAIK, when I execute</p> <pre><code>java -Xms256M -Xmx1280M -jar osgi-3.4.2-R34x_v20080826-1230.jar </code></pre> <p>It reads config.ini so with equinox.common and update.configurator bundles it "detects" all bundles deployed in /plugins folder. After that, the ConfiguratorModule (a custom bundle) just reads all bundles in the context and executes start method of each one (bundleA and bundleB). I have an eclipse project (bundleC), which uses some clases defined in bundleA and bundleB, so the MANIFEST.MF is:</p> <pre><code>Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: BundleC Plug-in Bundle-SymbolicName: com.test.bundlec Bundle-Version: 1.0.0 Bundle-Activator: com.test.bundlec.Activator Import-Package: javax.naming,javax.sql,org.osgi.framework;version="1.3 .0",org.osgi.util.tracker;version="1.3.1" Bundle-ClassPath: . Require-Bundle: com.test.BundleA;bundle-version="1.0.0", com.test.BundleB;bundle-version="1.0.0" </code></pre> <p>So, I want to generate a plugin (jar) file for the bundleC project. As there are two bundles in the "Require-bundle" option, those projects (BundleA and BundleB) should be in the bundleC classpath, isn´t it? So, in that case, I just generate the bundle (by exporting it as "Plugin Development") and place the new bundle in the plugin folder. Is there something I'm missing?</p> <p>Well, in case all I´ve said is correct, here is my problem. I have the plugin jar file for BundleA and BundleB but I don´t have the source code of them, so I get an error when exporting BundleC to a jar plugin because, as it seem obvious, it can´t find the required classes it uses from BundleA and BundleB. Is there any way to generate the plugin without those required-bundles in the classpath?</p> <p>I´ve tried to "decompile" them and then create the projects, and adding them in the classpath of BundleC. I can generate the plugin, then I place it in the plugins folder, but when execute the osgi enviroment, the bundleC is not found. What I´m doing wrong?</p> <p>Thanks for your answers</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USuser1093643
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POExporting a bundle with dependencies with another bundles
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPlease post the exact error you get, any stack traces etc
      singulars
      1. POExporting a bundle with dependencies with another bundles
      1. USkatsharp
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload