TESTING:- No middleware dependencies. No O/S dependencies. Problem:- Currently this will create a msg using the default payload rather than the payload in the file. To expose this create a file using

TESTING:- Not O/S or middleware specific. Checked example apps, all languages & on different middlewares to confirm that data is now flushed when redirected to file. Specifically:- 1. mamapublisherc /

TESTING:- **Windows only** No middleware dependencies. Will need to run MamaFtMember c# in bridge mode, both before & after the fix. Before the fix the previous version will hang, after the addition o

TESTING:- Again from list discussed with Damien - Reservedfieldsimpl.h missing declaration in openmama. This was a simple addition of missing declaration for cleanupReservedFields within reservedfield

TESTING:- Again from list discussed with Damien - 15) Priceimpl.c - lld? Looks wrong in openmama. snprintf (buf, bufMaxLen, "%lld", integer); Luckily, every version of VS since 2005 seems to support '

TESTING:- This was requested for submission by Damian from the list of differences between openmama & the enterprise versions. forcevalog patch needed sent out, which is used to add a custom prefix to

Testing :- This is not OS dependent This is not middleware dependent The below patches were as discussed with Damian to remove all the commented out sections of dead code from the fieldcache files in

Emmanuel, thanks for this fix, I'm sending it to the OpenMAMA developers for inclusion upstream

Hi We have just come across this little oddity and wonder if anyone can throw any light on what is supposed to be happening I notice from the source to the C# implementation of Open Mama 2.3.0, that t

In some MAMA FT Timers, the timer callback always reports that it is a "multicast" FT type, when in fact that code is shared for all FT types. This is misleading to the MAMA application developer who

Morning all, I'm aware there's a few of you out there who would be interested in contributing further to OpenMAMA, but who aren't really sure of where to start. As such, we've started to pull together

[Note: This is a cross-post from the Library Manager Working Group - If you're not familiar with the goals of the working group or the library manager project, please refer to the links within the rel

Testing - This is not OS Dependant This applies to C++ only Only the mamatransport exception was possible to recreate To test this simply get build and run the attached application, MamaTransportTest.

Testing – This is required for warning fixes within mamaconsumer application. This was tested using the mamaconsumer application. Run application & check output is reflected correctly. From 7cf7227817

Testing This is not OS dependant This is not middleware dependant This is a subtle race condition which could not be recreated directly with a MAMA application. We were able to recreate it consistentl

Testing Build OpenMAMA with docs and review the associated html files. From a1a8d0cafb5093e95cbf07b4f6bee7c50afb888b Mon Sep 17 00:00:00 2001 From: Gary Molloy <gmolloy@...> Date: Mon, 23 Jun 2014 14:

Testing Fixed compiler warnings should not affect the building or running of any related MAMA clients. Simply try building OpenMAMA and running regression tests and unittests. From 460bcfbb2c5525cc197

Testing No Middleware dependencies. Applies to C# Only. Run the C# example application MamaListenCS.cs: First in quiet mode (-q), you should expect to see no data other than the message info, Symbol,

Testing This is not OS dependant . This applies to JAVA only. This can only be tested on a middleware that provided topic callbacks. Run the attached MamaProxy.java test application and then subscribe

Testing To test this simply run the attached MamaProxy_OMAMA-265.java example application. This will test getCache() for both the MamaDQPublisher and MamaDQPublisherManager. Expect to see the followin