From 09f5cffa90d805eaf2c92e63cc676b51bb25a9b4 Mon Sep 17 00:00:00 2001 From: Martin Vajnar Date: Sat, 2 May 2015 13:38:35 +0200 Subject: [PATCH] shape_android: do not enforce ByteOrder Setting of ByteOrder by user is not supported for publications. That is on the Java part we discover, what the native ByteOrder is and set it accordingly (see MessageData() constructor at orte/java/src/org/ocera/orte/types/MessageData.java:41). On the C side it is assumed, that the byte order is also native (see ORTEPublicationSendLocked() at orte/liborte/ORTEPublication.c:316). But if we set the ByteOrder of publisher different than native on the Java part, than in liborte it is still believed to be native causing problems during deserialization. --- .../shape_android/src/org/ocera/orte/shape_android/BoxType.java | 1 - 1 file changed, 1 deletion(-) diff --git a/orte/contrib/shape_android/src/org/ocera/orte/shape_android/BoxType.java b/orte/contrib/shape_android/src/org/ocera/orte/shape_android/BoxType.java index d9e8d08..a51f3e7 100644 --- a/orte/contrib/shape_android/src/org/ocera/orte/shape_android/BoxType.java +++ b/orte/contrib/shape_android/src/org/ocera/orte/shape_android/BoxType.java @@ -59,7 +59,6 @@ public class BoxType extends MessageData } this.allowScaling = true; - this.buffer.order(null); // set buffer to Little endian (Shape uses this) } /* (non-Javadoc) -- 2.39.2