I've checked the bug database [1], JEPs list [2] and Google but this
JEP appears to have disappeared. Can this be confirmed?
Stephen
[1] https://bugs.openjdk.java.net/issues/?jql=issuetype%20%3D%20JEP
[2] http://openjdk.java.net/jeps/0
On 13 February 2014 at 11:05, Florian Weimer wrote:
> On 01/
On 01/23/2014 03:30 PM, Chris Hegarty wrote:
On 22 Jan 2014, at 15:14, Florian Weimer wrote:
On 01/22/2014 03:47 PM, Chris Hegarty wrote:
On 22/01/14 13:57, Florian Weimer wrote:
On 01/14/2014 01:26 AM, mark.reinh...@oracle.com wrote:
Posted: http://openjdk.java.net/jeps/187
There's anoth
Am 22.01.2014 um 17:33 schrieb "David M. Lloyd" :
> The concept of explicit deserialization constructors is interesting and is
> something I've explored a little bit in the context of JBoss Marshalling.
...
> The idea with a serialization-aware constructor is that each serializable
> class cons
Hi David,
This is a nice summary of how object deserialization is working today, and some
interesting ideas around serialisation-aware constructors.
It seems there is just too much magic in the construction of deserialized
objects. All the field values required to fully construct the object are
On 22 Jan 2014, at 15:14, Florian Weimer wrote:
> On 01/22/2014 03:47 PM, Chris Hegarty wrote:
>> On 22/01/14 13:57, Florian Weimer wrote:
>>> On 01/14/2014 01:26 AM, mark.reinh...@oracle.com wrote:
Posted: http://openjdk.java.net/jeps/187
>>>
>>> There's another aspect of the current appro
Am 22.01.2014 um 17:33 schrieb "David M. Lloyd" :
> The concept of explicit deserialization constructors is interesting and is
> something I've explored a little bit in the context of JBoss Marshalling.
...
> The idea with a serialization-aware constructor is that each serializable
> class const
On 01/13/2014 06:26 PM, mark.reinh...@oracle.com wrote:
Posted: http://openjdk.java.net/jeps/187
The concept of explicit deserialization constructors is interesting and
is something I've explored a little bit in the context of JBoss Marshalling.
The way construction works today (simple versi
On 01/22/2014 03:47 PM, Chris Hegarty wrote:
On 22/01/14 13:57, Florian Weimer wrote:
On 01/14/2014 01:26 AM, mark.reinh...@oracle.com wrote:
Posted: http://openjdk.java.net/jeps/187
There's another aspect of the current approach to serialization that is
not mentioned: the type information do
On 22/01/14 13:57, Florian Weimer wrote:
On 01/14/2014 01:26 AM, mark.reinh...@oracle.com wrote:
Posted: http://openjdk.java.net/jeps/187
There's another aspect of the current approach to serialization that is
not mentioned: the type information does not come from the calling
context, but excl
On 01/14/2014 01:26 AM, mark.reinh...@oracle.com wrote:
Posted: http://openjdk.java.net/jeps/187
There's another aspect of the current approach to serialization that is
not mentioned: the type information does not come from the calling
context, but exclusively from the input stream. This mea
Posted: http://openjdk.java.net/jeps/187
- Mark
11 matches
Mail list logo
