1:38 p.m.
With JAXB being part of the JDK in Java 8, Hibernate ORM doesn't list
it as a runtime dependency.
Java 9 users have been suggested to use the JVM option "--add-modules
java.xml.bind" to avoid the JVM hiding the JAXB library from
classpath.
With Java 11 the java.xml.bind is no longer available; what should we
suggest to users?
Should we list it as an explicit dependency in the released pom files?
Thanks,
Sanne
3:30 p.m.
+1 for listing the API dependency "javax.xml.bind:jaxb-api". Not sure
about the implementation though, maybe we can use
"com.sun.xml.bind:jaxb-impl" as an optional dependency?
Mit freundlichen Grüßen,
------------------------------------------------------------------------
*Christian Beikov*
Am 02.05.2018 um 20:38 schrieb Sanne Grinovero:
4:30 p.m.
On 2 May 2018 at 21:38, Marko Bekhta <marko.prykladna(a)gmail.com> wrote:
Why not move to Stax as we've done in HV? It'll be more
consistent this way.
+1
that would be my preference, but it's longer term.
It will require quite some more work - especially for Hibernate ORM.
For now I'm wondering if we can be more helpful with the current
versions, especially 5.3 which is about to be released. At very least
I'd like to document the needs but I'm not entirely sure myself if we
should list specific versions (and which ones), it all seems to vary
on the JDK being used.
Thanks,
Sanne
4:24 p.m.
On 2 May 2018 at 21:30, Christian Beikov <christian.beikov(a)gmail.com> wrote:
Hi Christian,
right that's what makes it confusing. We might want to list the
jaxb-api explicitly but it's not enough to make it work: people will
need to know to list several more dependencies.
This is what I've been experimenting with in the Search testsuite
(which uses Hibernate ORM):
<!-- All replacements for JAXB -->
<dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-core</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>javax.activation</groupId>
<artifactId>javax.activation-api</artifactId>
<scope>provided</scope>
</dependency>
I'm afraid that we might as well not list jaxb-api as users need to
understand this all either way.
Thanks,
Sanne
4:39 p.m.
Hi Sanne,
On Wed, May 2, 2018 at 11:24 PM, Sanne Grinovero <sanne(a)hibernate.org>
wrote:
<dependency>
Not sure where you got these dependencies.
I think the one we should use is the following:
<groupId>org.glassfish.jaxb</groupId>
<artifactId>jaxb-runtime</artifactId>
(which comes with quite a few transitive dependencies unfortunately)
JAXB is currently maintained here: https://javaee.github.io/jaxb-v2/.
HTH
--
Guillaume
4:50 p.m.
On 2 May 2018 at 22:39, Guillaume Smet <guillaume.smet(a)gmail.com> wrote:
The org.glassfish stuff is legacy / deprecated. You should use the
groupId javax.xml.bind now.
Great example of the kind of confusion I'd like to avoid every user to have :)
JAXB is currently maintained here: https://javaee.github.io/jaxb-v2/.
That's right, and uses "javax.xml.bind" if you check its sources.
5:07 p.m.
On Wed, May 2, 2018 at 11:50 PM, Sanne Grinovero <sanne(a)hibernate.org>
wrote:
Maybe my quote wasn't clear enough but I was talking about the impl (the
jaxb-impl I quoted), not the API.
See
https://github.com/javaee/jaxb-v2/blob/master/jaxb-ri/runtime/impl/pom.xml .
Great example of the kind of confusion I'd like to avoid every user to have
:)
And to have some fun, take a look at the Maven coordinates of the parent of
the above link :).
For the API, not the runtime/impl.
--
Guillaume
4:40 p.m.
You are right that people will have to add some other dependencies if
they want to use Hibernate on Java 9+, but IMO we should at least put
the dependencies into the pom.xml that we have a hard dependency on
which in this case is the jaxb-api or in module descriptor speak the
"java.xml.bind" module.
People will have to adapt to this and add their own JAXB implementation,
just like they now use Hibernate as JPA implementation.
Mit freundlichen Grüßen,
------------------------------------------------------------------------
*Christian Beikov*
Am 02.05.2018 um 23:24 schrieb Sanne Grinovero:
4:55 p.m.
I actually think since the bootclasspath has precedence over the user
classpath, nothing will happen. It's just that there is an additional
JAR that needs to be downloaded.
If it's an implementation with zero further dependencies, it might
actually be an ok solution to add the dependency, as users could simply
exclude the dependency if they like without messing up other transitive
dependencies.
Mit freundlichen Grüßen,
------------------------------------------------------------------------
*Christian Beikov*
Am 02.05.2018 um 23:48 schrieb Guillaume Smet:
2515
days inactive
2515
days old
10 comments
4 participants
participants (4)
-
Christian Beikov -
Guillaume Smet -
Marko Bekhta -
Sanne Grinovero