Hello Carlos and Alex. After digging a bit further i noticed that WebORB is expecting 2 additional properties in the remoting request than what AbstractMessage.as is sending.
AbstractMessage.as sends: body clientId destination headers messageId timestamp timeToLive WebORB is expecting... body clientId destination headers messageId timestamp timeToLive AND operation correlationId This could be why the WebORB parser is throwing an exception. Your thoughts? Regards -- Sent from: http://apache-royale-users.20374.n8.nabble.com/
