Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>When you embed any jar via Embed-Dependency tag then the maven-bundle-plugin would analyze that jar also and add the referred packages to the host bundle Import-Package list. Mostly such packages are optional depending on the feature used. For example in your usecase the H2 jar has dependency on Lucene, Servlet API for certain features. if your usage scenario does not require these features then you can mark these packages as optional</p> <pre class="lang-xml prettyprint-override"><code>&lt;plugin&gt; &lt;groupId&gt;org.apache.felix&lt;/groupId&gt; &lt;artifactId&gt;maven-bundle-plugin&lt;/artifactId&gt; &lt;version&gt;2.3.5&lt;/version&gt; &lt;extensions&gt;true&lt;/extensions&gt; &lt;configuration&gt; &lt;obrRepository&gt;NONE&lt;/obrRepository&gt; &lt;instructions&gt; &lt;Bundle-SymbolicName&gt;${project.artifactId}&lt;/Bundle-SymbolicName&gt; .. &lt;Embed-Dependency&gt; h2 &lt;/Embed-Dependency&gt; &lt;Import-Package&gt; org.osgi.service.jdbc.*; org.apache.lucene.*; javax.transaction.*;resolution:=optional, * &lt;/Import-Package&gt; &lt;/instructions&gt; &lt;/configuration&gt; &lt;/plugin&gt; </code></pre> <p>In above config we mark such packages as optional. The main problem is to determine the package list depending on your usage</p> <p>One quick and dirty way is to mark all as optional imports. <strong><em>Should be used as a last resort</em></strong>. As some valid imports would be marked optional and OSGi fwk would not be able to check them.</p> <pre class="lang-xml prettyprint-override"><code> &lt;Import-Package&gt; *;resolution:=optional &lt;/Import-Package&gt; </code></pre> <p>Also note that H2 jar is a valid OSGi bundle so you can deploy it directly.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to handle Import-Package entries which come from jars on the Bundle-Classpath?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USChetan
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMarking packages as optional is dangerous, unless the code that is using those packages really was designed to treat such packages as optional. In other words, if the code does end up trying to use code from such a package, you will get an exception. If you're really don't use the code, you might as well suppress the import altogether, which saves the resolver the trouble of even trying to find that package.
      singulars
      1. PO
      1. USMarcel Offermans
    2. CO@MarcelOffermans I fully agree that marking packages optional blindly is dangerous. The problem is many times when wrapping thirdparty jar the user is not aware of which packages are really optional. Another approach I typically take is add such packages to Dynamic-Import list. However the maven-bundle-plugin does not expands the wildcard for DynamicImport-Package instruction so coming up with list is not straightforward
      singulars
      1. PO
      1. USChetan
    3. COThe plugin does not expand wildcards for DynamicImport-Package because the header itself supports wildcards, so expanding them would be the wrong thing to do.
      singulars
      1. PO
      1. USMarcel Offermans
 

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