[xstream-scm] [jira] (XSTR-767) Serializing lambda expressions fails with XStream and JDK 1.8u40

[JIRA]

Title: Message Title

Jörg Schaible commented on an issue   Re: Serializing lambda expressions fails with XStream and JDK 1.8u40 Hi Tobias, some general remarks about lambda expressions first: XStream will never be able to unmarshal XML generated for unserializable lambda expressions, since the object (and therefore the XML) lacks any useful information to recreate such an instance. A serialized lambda _expression_ uses a replacement object of type java.lang.invoke.SerializedLambda. XStream is already capable of marshal and unmarshal such serializable lambda expressions. The class name of the recreated lambda _expression_ is different, it seems those names are kind of temporarily unique. The information of the SerializedLambda seems compiler specific. For me the value "implMethodName" name differs depending on the compiler. The internal Eclipse compiler has generated a name like "lambda$0" while my Oracle JDK 8 compiler generates a name like "lamdba$theMethodName$hex$1". As result one of my lambda serialization test fails in Eclipse, when I used the original compiler to generate the class file or in Maven's surefire, when Eclipse created it (NPE in SerializedLambda#readResolve). Might be an Eclipse compiler bug, but I've recognized that your XML contains names like generated from Eclipse compiled classes. However, you have a more specific problem. The exception provides the XPath to the problematic XML element. If you format the provided XML (you gzipped the attachment twice), it is in line 1840: <val_-visibilityFunction class="com.vodecc.voipmng.boundary.wicket.general.PageWithMenu$$Lambda$130/1880580028" reference="../../../../../../../../../../../../../../../data/com.vodecc.voipmng.boundary.wicket.general.menu.MenuBar/children/list/com.vodecc.voipmng.boundary.wicket.general.menu.Menu_-WicketMenu[2]/children/list/com.vodecc.voipmng.boundary.wicket.general.menu.Menu_-WicketMenu/children/list/com.vodecc.voipmng.boundary.wicket.general.menu.MenuEntry_-2[3]/val_-visibilityFunction"/> While you marshal serializable lambda expressions, you try to use the same instance in multiple places and XStream therefore references it. However, since class names of lambda expressions cannot be loaded, it fails here. I'll have to investigate further. Add Comment   XStream / XSTR-767 Serializing lambda expressions fails with XStream and JDK 1.8u40 It seems we're not able to deserialize Lambda expressions with XStream 1.4.7 The code in question looks roughly like this: @FunctionalInterface public interface Visible extends Serializable {     public boolean isVisible(); } public interface IMenuItem extends Serializable {     // ... stuff omitted ... } public abstract class AbstractMen... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email