[
https://issues.apache.org/jira/browse/DERBY-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16966596#comment-16966596
]
Christoph Läubrich commented on DERBY-7056:
-------------------------------------------
Sorry somwhere missed the last comments. The old Activator registered the
driver with the DriverManager, this is often problematic due to the static
access and afaik also deprecated by java itself as it is now possible to use
the SPI-Meachnism in traditional java application, so I think we can drop this.
Thats also why you see this exception, the activator tries to shutdown all
databases, but the code that executes this can't access the required classes.
We will instead need an Activator for the JDBC-Service, so I would recommend to
just remove all code from stop/start but keep the activator for later
extensions.
> 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
> Attachments: derby.txt
>
>
> 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)
