Adding module causes classloading issues

[Gunnar Morling]

Hi,

There's a preview version of JBoss' instance of the JTA API JAR without the
XA classes available already:


http://search.maven.org/#artifactdetails%7Corg.jboss.spec.javax.transaction%7Cjboss-transaction-api_1.2_spec%7C2.0.0.Alpha1%7Cjar

--Gunnar


2017-11-28 13:54 GMT+01:00 Stephen Felts <stephen.felts at oracle.com>:

> I'm trying to get javax.transaction-api-1.3-ea.jar published to Maven
> Central as soon as possible.
> In the meantime, you can make your own if you are blocked by starting with
> javax.transaction-api-1.2.jar, deleting the three classes in the
> javax.transaction.xa  package, and updating  META-INF/MANIFEST.MF to add
> Automatic-Module-Name: java.transaction
>
> -----Original Message-----
> From: Alan Bateman
> Sent: Tuesday, November 28, 2017 5:49 AM
> To: Michael Hall <mik3hall at gmail.com>
> Cc: jigsaw-dev at openjdk.java.net
> Subject: Re: Adding module causes classloading issues
>
> On 28/11/2017 09:14, Michael Hall wrote:
> > It’s a little alarming jdeps might report false dependencies? I would
> > rather spare you the full output. How about…
> >
> > jdeps halfpipe.jar | grep corba
> > halfpipe.jar -> java.corba
> >     org.cmdline                                        -> javax.rmi
>                                     java.corba
> I assume `jdeps -verbose:class` will reveal that there is some in the
> org.cmdline package with a reference to javax.rmi.PortableRemoteObject.
> That class isn't used much beyond RMI-IIOP and maybe something you can
> drop if an alternative is possible.
>
>
> > :
> >
> >
> >> As Alex mentioned, this case is crying out for the XA-less JTA that
> Alex mentioned. Hopefully the JSR 907 spec lead will sort this out soon.
> > Also a little sorry to hear the code is crying out but again it may be
> best to put it on hold then.
> >
> Once there is a version of java.transaction published to Maven without the
> XA package then it will be a lot simpler.
>
> -Alan
>