[DBCP-571] Back to OSGi import of `javax.transaction.xa` package

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Grzegorz Grzybek
• Created: 01/Feb/21 16:44
• Updated: 27/Jul/22 08:50

Description

I'd like to refer to DBCP-445 and DBCP-454 issues, which left commons-dbcp2 OSGi bundle with these headers:

Import-Package = 
...
	javax.transaction;version=1.1.0,
	javax.transaction.xa;mandatory:=partial;partial=true;version=1.1.0,

I've described some findings in https://github.com/ops4j/org.ops4j.pax.transx/issues/33 and I'd like to know what's the rationale behind this "partial" attribute?

First, javax.transaction.xa package is complete in both JDK 8 and 9+ (JPMS) and it's not missing any class in JDK itself.
javax.transaction on the other hand do miss important classes and if anything, this package should be special, not javax.transaction.xa.

I'll do some resolution test with Karaf and will add more comments later. But if you (DBCP2 devs) know more about the mentioned issues, I'd be happy to learn more

Issue Links

• is related to: KARAF-6715 Wrong exports of javax.transaction package from jre.properties
• relates to: KARAF-7032 JTA specification/package versions and exports are still not perfect