Adding module causes classloading issues

[Alan Bateman]

On 28/11/2017 02:00, Alex Buckley wrote:
>
> Thank you, for investigating how your app relates to CORBA, JTA, and 
> Attach. I hope http://openjdk.java.net/jeps/8189188 was informative at 
> least. Alan will probably be along shortly with some points I missed.
One point that I didn't see mentioned in the thread so far is a detail 
in the JEP 261 policy on root modules for the case that module java.se 
is not observable. When java.se is not observable then all modules 
(system or upgrade module path) that export an API are resolved. The 
output of `java --list-modules` will answer his quickly but I'll bet the 
image doesn't have java.se.

I don't know what halfpipe is but it would be interesting to paste in 
the detailed output from jdeps so we can see if it really depends on 
classes in java.corba. I'm also interested in the first mail about "JMX 
Attach" as it's not clear what that means. Is jconsole or VisualVM in 
the picture? This would require the java.management.rmi module to be 
included.

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.

-Alan