-
Thanks Taras,
Unless I don't use the Harmony sources as the stating point, it may be better to create a wrapper class that implements all the methods, modifying where necessary before delegating them to the Java 1.4 API class. This could then be contributed back under a BSD License?
What are your thoughts, can you see any traps in this approach?
Cheers,
Peter.
2009-04-12 03:28:15 UTC in Retrotranslator
-
Thanks Taras,
I'm going to have a go at implementing backports of ObjectInputStream/ObjectOutputStream, do you want a copy for your project site when complete? The sources will be under the Apache License of course?
Cheers,
Peter.
2009-04-02 10:25:52 UTC in Retrotranslator
-
Hi Taras,
Just had a little play, I get it now, I think. Retrotranlator doesn't attempt to support Serialization of API implementation / backported classes, since the class fully qualified names are different, so that a transformed class can run on a later platform without stepping on the java namespace.
bash-3.00$ serialver net.sf.retrotranslator.runtime.java.lang.Enum_...
2009-04-01 09:01:24 UTC in Retrotranslator
-
Just a quick update,
Looks like you can't modify the serialVersionUID of an enum, its always 0L. Wishful thinking on my part ; )
Cheers,
Peter.
2009-04-01 05:59:44 UTC in Retrotranslator
-
Thanks Taras,
Neat program by the way ;) I like the elegant way you've enabled extensions to Retrotranslator.
Getting into detailed specifics (please forgive me):
For a JDK 1.5 application and a translated one, interoperating via serialization (I'm only interested in Value classes, not things that shouldn't be serialized).
Case 1:
Where a class such as String that is compatible...
2009-04-01 00:42:16 UTC in Retrotranslator
-
How does Retrotranslator affect serialized objects?
Is there some documentation that identifies which objects are safe to Serialize and those that aren't?
Best Regards,
Peter.
2009-03-31 03:37:16 UTC in Retrotranslator
