Example of closure in EMA

Asking on behalf of a client, please provide a simple example making use of closure in EMA Java to map subscriptions back to my own objects.
Best Answer
-
A general usage of closure is to be as an identifier (the application-specific purpose) of item subscriptions. So that the application can distinguish an event received in the callback methods by checking the closure object.
Here this is the example code (modified from example100 MarketPrice_Streaming):
** Calling registerClient using a closure object**
AppClient appClient = new AppClient();
OmmConsumerConfig config = EmaFactory.createOmmConsumerConfig();
consumer = EmaFactory.createOmmConsumer(config.host("<host>:<port>").username("<username>"));
ReqMsg reqMsg = EmaFactory.createReqMsg();
// equity ric group
consumer.registerClient(reqMsg.clear().serviceName("<serviceName>").name("IBM.N"), appClient, "EQUITY_CLOSURE");
consumer.registerClient(reqMsg.clear().serviceName("<serviceName>").name("TRI.N"), appClient, "EQUITY_CLOSURE");
// currency ric group
consumer.registerClient(reqMsg.clear().serviceName("<serviceName>").name("JPY="), appClient, "CURRENCY_CLOSURE");
consumer.registerClient(reqMsg.clear().serviceName("<serviceName>").name("GBP="), appClient, "CURRENCY_CLOSURE");
consumer.registerClient(reqMsg.clear().serviceName("<serviceName>").name("EUR="), appClient, "CURRENCY_CLOSURE");
// chain ric group
consumer.registerClient(reqMsg.clear().serviceName("<serviceName>").name("0#.SETI"), appClient, "CHAIN_CLOSURE");
// etc ric group
consumer.registerClient(reqMsg.clear().serviceName("<serviceName>").name("THIS_IS_A_NON_EXISTING_RIC"), appClient, "ETC_CLOSURE");** Printing a closure object in the callback method **
public void onRefreshMsg(RefreshMsg refreshMsg, OmmConsumerEvent event)
{
System.out.print("onRefreshMsg: \t");
System.out.print(refreshMsg.name());
System.out.print("\t");
System.out.println(event.closure());
}
public void onUpdateMsg(UpdateMsg updateMsg, OmmConsumerEvent event)
{
System.out.print("onUpdateMsg: \t");
System.out.print(updateMsg.name());
System.out.print("\t");
System.out.println(event.closure());
}
public void onStatusMsg(StatusMsg statusMsg, OmmConsumerEvent event)
{
System.out.print("onStatusMsg: \t");
System.out.print(statusMsg.name());
System.out.print("\t");
System.out.println(event.closure());
}** Here this is the result **
onRefreshMsg: IBM.N EQUITY_CLOSURE
onRefreshMsg: JPY= CURRENCY_CLOSURE
onRefreshMsg: EUR= CURRENCY_CLOSURE
onRefreshMsg: 0#.SETI CHAIN_CLOSURE
onRefreshMsg: GBP= CURRENCY_CLOSURE
onStatusMsg: THIS_IS_A_NON_EXISTING_RIC ETC_CLOSURE
onRefreshMsg: TRI.N EQUITY_CLOSURE
onUpdateMsg: JPY= CURRENCY_CLOSURE
onUpdateMsg: JPY= CURRENCY_CLOSURE
onUpdateMsg: JPY= CURRENCY_CLOSURE
onUpdateMsg: JPY= CURRENCY_CLOSURE
onUpdateMsg: EUR= CURRENCY_CLOSURE
onUpdateMsg: EUR= CURRENCY_CLOSUREHope this helps!
0
Answers
-
Thanks @Nipat Kunvutipongsak that helps.
Users should note that closure doesn't have to be a static string, it can be a pointer to your object or an index to your structure and it can be unique for every item or it can group items as in this example.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛