Enum interop between 0.5.5 and msgpack-java 0.6.11 about msgpack-cli HOT 3 CLOSED

(I removed previous post because I found the cause while I reproduced issue #46, and edit at 15:15)

Hi @JamesWM
Sorry for inconvinience and delay.

I found it is by design to work around C# and CLR reflection API desigin -- they DO NOT gurantee the order of the field. MessagePack CLI sorts membres in lexical order to avoid future incompatibility of stored data. So your MessageDescriptor might be serialized as [<messageId>, <version>], so the version=1 was deserialized as messageId.

Please try to put [MessagePackMembrer(n)] attributes to your fields to specify explicit order like:

public class MessageDescriptor
{
    [MessagePackMember(0)]
    public byte version = 1;
    [MessagePackMember(1)]
    public MessageId messageId;
    ...
}

-Note: I guess an annotation to specify order is needed in Java (see http://docs.oracle.com/javase/7/docs/api/java/lang/Class.html#getDeclaredFields%28%29 , it states that the order returned from reflection API is undefined in Java too), but I am not expart of MessagePack Java (@Index annotation looks help you)-

from msgpack-cli.

Ok - similar to issue 46. I will try this and update with results (might be a day or two).

from msgpack-cli.

Got around to testing this, and it works as long as:

There are @Index attributes for each of the enum members in the java class, and the @Index values are zero-based, and the enum values are also 0-based, and their values are all equal to the @Index attribute values.

...and the same is true on the C# side, with the enum attributed with [MessagePackEnum(SerializationMethod=EnumSerializationMethod.ByUnderlyingValue)]

...then I can get enum's to interoperate between the languages.

from msgpack-cli.