Re: Loading MamaMsg from dictionary
Damian Maguire <DMaguire@...>
In answer to your first question, yes the getDictionaryMessage method uses the default payload bridge for generating the dictionary message. At present there's no way to create a dictionary message for other currently loaded payloads, though I suspect an implementation would be straight forward. If you'd like to raise a bugzilla ticket (http://bugs.openmama.org) describing the issue, we'll be able to track it and someone in the community may be able to pick it up. Obviously, if you'd like to submit a patch yourself it would be greatly appreciated.
As a work around, it would be possible to iterate the dictionary message generated by the default payload, and push the details into a message for the alternative payloads. This would be similar to the mechanism used by the captureconvert application found in mama/c_cpp/src/testtools/captureconvert/c/. It's certainly not an ideal approach, and would be better managed internal to MAMA, but it should work in the interim.
From: <Alpert>, Reed <reed.alpert@...>
Date: Monday, February 10, 2014 6:15 PM
To: "openmama-users@..." <openmama-users@...>
Subject: [Openmama-users] Loading MamaMsg from dictionary
The C++ MamaDictionary has a MamaMsg* getDictionaryMessage()method.
Does this use the payload of the default bridge?
If multiple bridges are loaded, and need to have dictionaries published to them, is there a way to create dictionary messages with the native payload for each bridge?
Reed Alpert | Corporate & Investment Bank | PIM Trading Technology | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198 | M: 917.414.4613 | reed.alpert@...
Alternate Contact: CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...
This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.
This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange Group, Inc. (ICE), NYSE Euronext or any of their subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.