[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16955394#comment-16955394
]
Christoph Läubrich commented on DERBY-7056:
-------------------------------------------
Maybe we are already closer as we thought, I checked out the source and noticed
the following:
# It already contains an activator
org.apache.derby.engine/org/apache/derby/osgi/EmbeddedActivator even though it
uses driver manager for static binding what is often not optimal, there is
already an entrypoint to add OSGi-JDBC Service as a better alternative
# compiled with "buildjars" a jar file is created (derby.jar) that already
contains required OSGi-Manifest header
I did not checked yet how they are created (the build.xml is rather complex),
but maybe its just necessary to tweak these a bit [~io7m] do you think you can
test this jar and tell whats missing from your point of view, or issue you are
encounter? If all is fine I think we can simply proceed adding JDBC Service and
thats it.
> 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
> Assignee: 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)
