Hi Alan,
I think this looks fine and of course I am OK with where you moved
javax.transaction.xa
I am not sure we need to have an MR for the SerialVersionUID given the
serialization spec defines how the default is calculated so just adding the
value does not change the behavior. I know it no
On Jan 5, 2015, at 7:12 AM, Alan Bateman wrote:
> On 03/01/2015 14:49, Lance Andersen wrote:
>> Hi Alan,
>>
>> I think this looks fine and of course I am OK with where you moved
>> javax.transaction.xa
>>
>>
>> I am not sure we need to have an MR for the SerialVersionUID given the
>> serial
On 1/3/15 2:01 AM, Alan Bateman wrote:
This is another update to the module graph, this time it's the
quagmire of the Java Transaction API, a subset of which is defined for
Java SE for mapping of CORBA exceptions to RMI exceptions and for the
XA support in the JDBC API.
The proposal is to c
On 03/01/2015 14:49, Lance Andersen wrote:
Hi Alan,
I think this looks fine and of course I am OK with where you moved
javax.transaction.xa
I am not sure we need to have an MR for the SerialVersionUID given the
serialization spec defines how the default is calculated so just
adding the val
This is another update to the module graph, this time it's the quagmire
of the Java Transaction API, a subset of which is defined for Java SE
for mapping of CORBA exceptions to RMI exceptions and for the XA support
in the JDBC API.
The proposal is to create a new module (named java.transacti
