Comment #1 on issue 170 by [email protected]: Keeping byte structure of
remote transactioId for TCAP Dialog
http://code.google.com/p/jss7/issues/detail?id=170
Here is a draft version of update (not yet commited into a master branch):
https://code.google.com/r/sergvetyutnev-jss7/source/detail?r=80c80b81e0e8d3ae7e70926cea6d86559314f200&name=map6
Update details:
- in primitives like TCBeginMessage, TCContinueMessage parameters
originatingTransactionId and destinationTransactionId changed long->byte[]
(and also getDestinationTransactionId(), setDestinationTransactionId, ...)
- DialogImpl.remoteTransactionId: changed long->byte[] (localTransactionId
did not changed)
- in class Utils two new methods have been added:
public static long decodeTransactionId(byte[] data) {
public static byte[] encodeTransactionId(long txId) {
They are used for encoding / decoding (nong<-->byte[]) for
DialogImpl.localTransactionId
