You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Grzegorz Grzybek (Jira)" <ji...@apache.org> on 2021/02/01 16:46:00 UTC
[jira] [Updated] (DBCP-571) Back to OSGi import of
`javax.transaction.xa` package
[ https://issues.apache.org/jira/browse/DBCP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grzegorz Grzybek updated DBCP-571:
----------------------------------
Description:
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 ;)
was:
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|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 ;)
> 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.3.4#803005)