[EMA C++] Get Illegible contents in updateMsg of brokers

luxiangyuan

hello:

I develop with EMA c++;

I request brokers with code such as "0874bk.HKd";

I get updateMsg through "cout << updateMsg << endl;"

But I get Illegible contents and Exception shown as follows:

So How can I deal with this problem ???

moragodkrit.chumsri_1

@luxiangyuan

• The original case you post is
  an error when you try to print updateMsg and get Illegible contents. It could
  be an issue from method toString inside UpdateMsg class when the content of
  fieldEntry contains RMTES encoded with a partial update. I just want to show you that I don't have the error when using the latest version. Actually, the recommended way to decode data is that the user has to decode field list and then check field type and decode it accordingly. Also Below special character, you see from my console output is a result when UpdateMsg class call toString to return value of fieldEntry inside the message. Typically, the class does not check the type of the field and it just returns value from toString method when you call cout << updateMsg <<endl;

value="ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ3440 2425ÍÍÍÍ98 4086"

You can see a similar value when calling fe.toString from the partial update message. See below sample codes to demonstrate the usage. Note that my sample just decodes only fid ROW80_4.

cout << "Name: " << fe.getName() << endl;
cout << "fe.toString:" << fe.toString() << endl;
rmtesBuffer.apply( fe.getRmtes() );
cout << "after call rmtestBuffer.apply()"<<rmtesBuffer.toString() << endl;

Sample console output

Item Name: 0874bk.HKd
Service Name: ELEKTRON_DD
Name: ROW80_4
fe.toString:FieldEntry fid="318" name="ROW80_4" dataType="Rmtes" value="ร5337รร1194 1193 -11s"
after call rmtestBuffer.apply() 5337 1194 1193 -11s | 5469 6825 9025 6999

The junk characters you see in original value is just the
data encoded with RMTES partial update so when we call rmtestBuffer.apply() it
will return the actual string which apply the change from partial field update.

• Regarding duplicate value from your screenshot, your codes seem to re-use the same rmtestBuffer object with any fields, therefore, it causes a duplicate data or redundant character. This should be incorrect usage.

Please note that the RMTES example just shows the way to
catch RMTES data for one specific field which is BCAST_TEXT. If you want to
apply the same approach to decode the HK page which contains multiple fields for Page rows, you
have to catch data for each row in the PAGE to your data structure such as Array of string
or array of RmtestBuffer class it depending on your design.

• Regarding the bug I mentioned, It’s the issue happen when you have codes that call fe.getRmtes().toString()
  before calling rmtestBuffer.apply(). You will get incorrect result from rmtesBuffer.toString(). That is the case I mentioned. If the application does not have the implementation like this, you don’t need to upgrade it.