[DERBY-1945] Need changes to manifest for OSGi environment

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 10.1.3.1
• Fix Version/s: 10.3.3.1, 10.4.2.1, 10.5.3.1, 10.6.1.0
• Component/s: Miscellaneous
• Urgency: Normal
• Assignee: Bryan Pendleton
• Reporter: Stephen Felts
• Created: 09/Oct/06 11:49
• Updated: 21/Jan/11 17:49
• Resolved: 19/Nov/09 23:38

Description

When running with Derby in an OSGi environment, there are a couple of changes that are needed in the manifest.

1. The manifest does not have a Bundle Symbolic Name. This causes some tools not to recognize it as an OSGi bundle and some things don't work nicely without the symbolic name.
Add Bundle-SymbolicName: derby to the manifest.

2. I'm working with a product that creates dynamic proxies for all of the interfaces like Connection, Statement, etc.
As part of doing that, it needs access to all classes that are referenced in those interface classes.
There are several classes that are referenced in packages that are not exported. The following exports needed to be added to the manifest:
org.apache.derby.iapi.jdbc
org.apache.derby.impl.jdbc

Issue Links

• is duplicated by: FELIX-272 Add SymbolicName to the Manifest
• relates to: DERBY-4574 derby.jar not a valid R4 OSGi bundle