Hi Joe, - correlationId is received from server (talking about BlazeDS always, since don't know about WebOrb), and is a String if small messages are off and a ByteArray if on. - operation is send from client and is 5 (client pong operation) in a normal RO operation (not SimpleRO) to establish connection with BlazeDS, then "operation" is the name of the method your are asking for. In SimpleRO instead of 5 is 13 (trigger connect operation) for the first connection.
So my guess is that something is wrong in your code I'll respond to the other email now 2018-08-10 1:19 GMT+02:00 JoeBoxer <[email protected]>: > 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/ > -- Carlos Rovira http://about.me/carlosrovira
