On Fri, 29 May 2026 11:37:07 GMT, Alan Bateman <[email protected]> wrote:

>> David Simms has updated the pull request with a new target base due to a 
>> merge or a rebase. The pull request now contains 2732 commits:
>> 
>>  - Merge remote-tracking branch 'valhalla/lworld' into 8317277
>>  - 8385344: [lworld] ProblemList 
>> tools/javac/platform/CanHandleClassFilesTest.java with --enable-preview
>>    
>>    Reviewed-by: fparain
>>  - 8385301: [lworld] Remove 
>> serviceability/sa/TestJhsdbJstackMixedWithXComp.java from problem list
>>    
>>    Reviewed-by: dsimms
>>  - 8385331: [lworld] adjust ValueComparisonTest.java again to work around 
>> JDK-8370769
>>    
>>    Reviewed-by: dsimms
>>  - 8385311: [lworld] TypePtr::eq() should use accessor method for _offset
>>    
>>    Reviewed-by: mchevalier
>>  - 8385259: [lworld] Clean up LP64 in x86 code
>>    
>>    Reviewed-by: dlong, thartmann
>>  - Merge
>>    
>>    Merge jdk-27+23
>>  - 8384924: [lworld] misc cleanups
>>    
>>    Reviewed-by: thartmann
>>  - 8385167: [lworld] C1: minor cleanups
>>    
>>    Reviewed-by: dlong, thartmann
>>  - 8384066: [lworld] TestDeadAllocationRemoval.java is ignored by jtreg
>>    
>>    Reviewed-by: thartmann
>>  - ... and 2722 more: https://git.openjdk.org/jdk/compare/86637704...b3b4a2cb
>
> src/java.base/share/classes/java/io/ObjectOutputStream.java line 170:
> 
>> 168:  *          {@code writeReplace}</a> method can provide a proxy object 
>> instead. That
>> 169:  *          object can then be serialized, and used to reconstruct the 
>> expected value
>> 170:  *          class instance at deserialization time.
> 
> The text in the preview-block aligns with the JEP 401 but I'm wondering how 
> to read this with java.lang.Integer or other migrated value class as an 
> example. Suppoer I writeObject an Integer to an ObjectOutputStream when 
> running with preview features enabled. It appears to serialize it even though 
> it is a value class and not a record. Maybe there is more in the 
> serialization spec that I need to read on this?
> 
> (The context for asking is really the indirect rather than direct case and 
> whether there is an issue with migrated value classes or not)

Yes, the serialization spec has special treatment for the 8 wrapper classes.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/31123#discussion_r3324922006

Reply via email to