[
https://issues.apache.org/jira/browse/DBCP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923203#comment-17923203
]
Marco commented on DBCP-571:
----------------------------
I'm working with my modified copy of this for quite a while now, and yet this
issue has not been integrated?!
If there are no plans on including this, I think it should be clearly spoken
out, and the issue closed.
I will update to 2.13 and add my manual patches again, but It would be great
not to have to keep a modified copy of this!
Thanks
> Back to OSGi import of `javax.transaction.xa` package
> -----------------------------------------------------
>
> Key: DBCP-571
> URL: https://issues.apache.org/jira/browse/DBCP-571
> Project: Commons DBCP
> Issue Type: Bug
> Reporter: Grzegorz Grzybek
> Priority: Major
>
> I'd like to refer to DBCP-445 and DBCP-454 issues, which left commons-dbcp2
> OSGi bundle with these headers:
> {noformat}
> Import-Package =
> ...
> javax.transaction;version=1.1.0,
> javax.transaction.xa;mandatory:=partial;partial=true;version=1.1.0,
> {noformat}
> 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|https://openjdk.java.net/projects/jigsaw/spec/]) 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 ;)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
