Update to existing patch “0003-Removed-some-compiler-warnings.patch” Some functions were hashed out when they should have been removed From 336e7fb506ef84c8d7c511103ecf9c73deff04ac Mon

TESTINGThis was a build fail when applying OpenMAMA patch – “MSVC - Visual Studio Solutions File Updates”There was simply a missing #include, any application that includes Lock.h but not

Build and check reference docs for MAMA C (search and file tree should now work correctly) From 7d4daa33f95ba93befe6bdeb18e059487a43d745 Mon Sep 17 00:00:00 2001 Message-Id:

Build and check reference docs for MAMA C From f800b198944a4035188cd93e975a468643c05701 Mon Sep 17 00:00:00 2001 Message-Id:

Build and check MAMA C reference docs From fe1b3020c1196a56deaefc425f5633ad25c9875b Mon Sep 17 00:00:00 2001 Message-Id:

Build and check reference documentation for MAMA C. From 5268a28a4b8755ebd078d1af39d25936fc6e8436 Mon Sep 17 00:00:00 2001 Message-Id:

Testing Running on RH5 gcc 4.1 shows warnings pre patch, missing after patch From 0e8aa6503fa2861fa4a03fc84888408d09b65127 Mon Sep 17 00:00:00 2001 Message-Id:

Testing This was not easily re-creatable but could be seen using enterprise products. The issue was seen to be resolved with the patch supplied. General regression and unittests were used to

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

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

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,

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

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,

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

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

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,

Afternoon all, The OpenMAMA 2.3.1 release branch has now been created, and the first release candidate has been tagged OpenMAMA-2.3.1-rc1. If you clone/update your local git repo, you should be able

Hi Folks, I've got a broker based Qpid Proton implementation here that I have been knocking together in my spare time. It needs a little bit of tidy up before I submit it, but it seems to work at the

Afternoon all, Following a few weeks of testing and some feedback from the community, we've decided to merge the field cache code into the next branch in advance of the 2.3.1 release. There are a few

[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