Non ASCII data getting published for Display Name

I'm uising below Java code to publish data. Recently there is an issue that Display Name has some non ascii chanarater. Please advise if there is any bug.

case MfFieldTypes.ALPHANUMERIC :
case MfFieldTypes.LONG_ALPHANUMERIC :
nestedFieldList.add(EmaFactory.createFieldEntry().ascii(fid, field_value ));
break;

Values at RIC for Display Name :

DSPLY_NAME "l

DSPLY_NAME " 4

Find more posts tagged with

java

ema-api

#technology

RMTES

Accepted answers

All comments

Jirapongse

@vikas.chaudhary

Thank you for reaching out to us.

Did you check this Encoding and Decoding non-ASCII text using EMA C# and Java article?

vikas.chaudhary

I have checked that but wondering how non ascii character got inserted to display name.

Jirapongse

That article has a sample code on GitHub.

Non ascii should be encoded in rmtes.

        fieldList.add(EmaFactory.createFieldEntry().rmtes(1352, emaBuffer)); //DSPLY_NMLL

Ascii can be encoded like this:

        fieldList.add(EmaFactory.createFieldEntry().ascii(260, "Simplified Chinese")); //SEG_FORW

vikas.chaudhary

but it seems that we are not publishing non ascii character

Jirapongse

What is the value in field_value?

nestedFieldList.add(EmaFactory.createFieldEntry().ascii(fid, field_value ));

vikas.chaudhary

vikas.chaudhary

Field Value is name of RIC which is String

Jirapongse

It looks like the field_value contains some junk data.

You may contact the API support team directly via Contact Premium Support to review the full code.

You will see the Contact Premium Support button if you are a RDC named user.

Jirapongse

Is the name of RIC in English?

vikas.chaudhary

yes..i

Jirapongse

If it is in UTF8, you may need to prefix it with:

0x1B 0x25 0x30

For example:

void ProcessMarketPriceRequest(RequestMsg reqMsg, IOmmProviderEvent providerEvent)

{

    // ...

    string utf8String = "伦敦证券交易所"; //Simplified Chinese

     // Set a byte array of RMTES three bytes escape sequence

    var bytesOne = new byte[] { 0x1B, 0x25, 0x30 };

    // Convert our UTF8 String to a byte array

    var bytesTwo = Encoding.UTF8.GetBytes(utf8String);

    // prepend 0x1B, 0x25, 0x30 to the UTF8 string

    byte[] byteRMTES = new byte[bytesOne.Length + bytesTwo.Length];

    for (int i = 0; i < byteRMTES.Length; ++i)

    {

        byteRMTES[i] = i < bytesOne.Length ? bytesOne[i] : bytesTwo[i - bytesOne.Length];

    }

}

Jirapongse

I tested it with the ex341_MP_OffStreamPost with the following code.

	public void onRefreshMsg(RefreshMsg refreshMsg, OmmConsumerEvent event)

	{
		String field_value = "TEST";

		System.out.println("Received Refresh. Item Handle: " + event.handle() + " Closure: " + event.closure());


		System.out.println("Item Name: " + (refreshMsg.hasName() ? refreshMsg.name() : "<not set>"));

		System.out.println("Service Name: " + (refreshMsg.hasServiceName() ? refreshMsg.serviceName() : "<not set>"));


		System.out.println("Item State: " + refreshMsg.state());


		if ( refreshMsg.domainType() == EmaRdm.MMT_LOGIN && 

				refreshMsg.state().streamState() == OmmState.StreamState.OPEN &&

				refreshMsg.state().dataState() == OmmState.DataState.OK )

			{

				PostMsg postMsg = EmaFactory.createPostMsg();

				RefreshMsg nestedRefreshMsg = EmaFactory.createRefreshMsg();

				FieldList nestedFieldList = EmaFactory.createFieldList();


				//FieldList is a collection in java

				nestedFieldList.add(EmaFactory.createFieldEntry().real(22, 34, OmmReal.MagnitudeType.EXPONENT_POS_1));

				nestedFieldList.add(EmaFactory.createFieldEntry().real(25, 35, OmmReal.MagnitudeType.EXPONENT_POS_1));

				nestedFieldList.add(EmaFactory.createFieldEntry().time(18, 11, 29, 30));

				nestedFieldList.add(EmaFactory.createFieldEntry().enumValue(37, 3));
				nestedFieldList.add(EmaFactory.createFieldEntry().ascii(5, field_value));


				nestedRefreshMsg.payload(nestedFieldList ).complete(true);


				((OmmConsumer)event.closure()).submit( postMsg.postId( postId++ ).serviceName( "DIST_PUB" )

															.name( "TRI.N" ).solicitAck( true ).complete(true)

															.payload(nestedRefreshMsg), event.handle() );

			}


		decode( refreshMsg );


		System.out.println();

	}

Then, I checked the XML trace file by enabling the XmlTraceToStdout configuration.

		<Consumer>
			<!-- Name is mandatory	-->
			<Name value="Consumer_1"/>
			<!-- Channel is optional: defaulted to "RSSL_SOCKET + localhost + 14002" -->
			<!-- Channel or ChannelSet may be specified -->
			<Channel value="Channel_1"/>
			<!-- Dictionary is optional: defaulted to "ChannelDictionary" -->
			<Dictionary value="Dictionary_2"/>
			<DictionaryRequestTimeOut value="0"/>
			<XmlTraceToStdout value="1"/>
		</Consumer>

The trace output shows that the data was published properly.



<!-- rwfMajorVer="14" rwfMinorVer="1" -->

<POST domainType="MARKET_PRICE" streamId="1" containerType="MSG" flags="0x66 (HAS_POST_ID|HAS_MSG_KEY|POST_COMPLETE|ACK)" postId="1" postUserId="0" postUserAddr="0.0.0.0" dataSize="46">

    <key flags="0x03 (HAS_SERVICE_ID|HAS_NAME)" serviceId="10000" name="TRI.N"/>

    <dataBody>

        <REFRESH domainType="MARKET_PRICE" streamId="0" containerType="FIELD_LIST" flags="0x40 (REFRESH_COMPLETE)" groupId="0" State: Open/Ok/None - text: "" dataSize="30">

            <dataBody>

                <fieldList flags="0x08 (HAS_STANDARD_DATA)">

                    <fieldEntry fieldId="22" data="0F22"/>

                    <fieldEntry fieldId="25" data="0F23"/>

                    <fieldEntry fieldId="18" data="0B1D 1E"/>

                    <fieldEntry fieldId="37" data="03"/>
                    <fieldEntry fieldId="5" data="5445 5354"/>   ⇐= TEST

                </fieldList>

            </dataBody>

        </REFRESH>

    </dataBody>

</POST>

You may need to test it with the ex341_MP_OffStreamPost example and enable the trace log to verify the published data.

vikas.chaudhary

its fine with most of RIC but failing for few.

Jirapongse

You may need to check the scope of this variable and identify which parts of the code can modify it.

In this case, you need to contact the API Support team directly via Contact Premium Support to investigate this issue on the application and EMA side.

Moreover, you can upgrade the application to use the latest version of EMA (RTSDK Java 2.3.2.L1 aka EMA/ETA 3.9.2.L1 aka 3.9.2.0).

EXPLORE OUR SITES