[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954228#comment-16954228
]
Christoph Läubrich edited comment on DERBY-7056 at 10/18/19 3:40 AM:
---------------------------------------------------------------------
There are two parts where Derby can help making integration in OSGi more smooth
# Adding Manifest-Header information (*required*): OSGi expects to have some
additional headers in the manifest, these can be added manually or automatic
(depending on the build system used, bnd is available as ant tasks or maven
plugin), if package structure does not change often the manual approach often
is suitable.
# Implementing the [Data Service Specification for
JDBC™|https://osgi.org/specification/osgi.cmpn/7.0.0/service.jdbc.html]
Technology ontop of the derby driver to help people to use the driver in an
osgi standardized way, this is essentially a thin wrapper you can find an
example here:
https://github.com/ops4j/org.ops4j.pax.jdbc/tree/master/pax-jdbc-derby/src/main/java/org/ops4j/pax/jdbc/derby/impl
to see what need to be done, even though this is optional it will help using
derby in OSGi without the need for additional libraries.
The good thing is, that both options only add code that is ignored when running
outside of an OSGi-Env so your other users won't notice any change.
Let me know if you need any further information, help or assistance.
was (Author: laeubi):
There are two parts where Derby can help making integration in OSGi more smooth
# Adding Manifest-Header information (*required*): OSGi expects to have some
additional headers in the manifest, these can be added manually or automatic
(depending on the build system used, bnd is available as ant tasks or maven),
if package structure does not change often the manual approach often is
suitable.
# Implementing the [Data Service Specification for
JDBC™|https://osgi.org/specification/osgi.cmpn/7.0.0/service.jdbc.html]
Technology ontop of the derby driver to help people to use the driver in an
osgi standardized way, this is essentially a thin wrapper you can find an
example here:
https://github.com/ops4j/org.ops4j.pax.jdbc/tree/master/pax-jdbc-derby/src/main/java/org/ops4j/pax/jdbc/derby/impl
to see what need to be done, even though this is optional it will help using
derby in OSGi without the need for additional libraries.
The good thing is, that booth options only add code that is ignored when
running outside of an OSGi-Env so your other users won't notice any change.
Let me know if you need any further information, help or assistance.
> Make Derby modules usable by OSGi-aware applications
> ----------------------------------------------------
>
> Key: DERBY-7056
> URL: https://issues.apache.org/jira/browse/DERBY-7056
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Affects Versions: 10.15.1.3
> Reporter: Richard N. Hillegas
> Priority: Major
>
> OSGi R7 introduced support for JPMS modules in 2018 according to
> https://blog.osgi.org/2018/02/osgi-r7-highlights-java-9-support.html. This
> includes additional information which goes into jar file manifests. Support
> for this OSGi information was requested by an email thread on the user list:
> http://apache-database.10148.n7.nabble.com/OSGi-manifest-headers-td150560.html.
> We need advice from OSGi experts on how to make Derby modules usable by
> OSGi-aware applications.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
