Unnamed module and duplicate package

[Alan Bateman]

On 11/03/2016 21:31, Alex Buckley wrote:
>
> A type in the java.sql module (javax.sql.XAConnection) returns a 
> javax.transaction.xa.* type. Therefore, the java.sql module would have 
> to depend on the tiny new module containing the javax.transaction.xa 
> package. The java.sql module is mapped to the bootstrap loader, so the 
> the tiny new module would have to be mapped to the bootstrap loader 
> too. That means it's not upgradeable, so there's little benefit in 
> carving it out at this time.
>
> The mapping of java.sql to the bootstrap loader also explains why the 
> javax.transaction.xa package hasn't been placed in the tiny existing 
> module java.transaction. Said module has been moved out of the 
> bootstrap loader, as part of the work to move java.corba out of the 
> bootstrap loader.
>
> tl;dr JDBC is a substantial shareholder in the javax.transaction.xa 
> package. 
Another point is that is that it would very troublesome to have a module 
in java.se depending on an upgradeable module. We need to keep the 
upgradeable modules in java.se.ee\java.se.

-Alan