Some changes have just been added to the origin/next branch! [Frank Quinn] Fix for null payload in createReusableMsg mama/c_cpp/src/c/bridge/qpid/SConscript mama/c_cpp/src/c/msg.c Results for

My bad (though a little concerning that passed unit tests - mental note taken to add a test around that) - try again now. Cheers, Frank

Classification:Public Hi Frank, Is it this commithttps://github.com/OpenMAMA/OpenMAMA/commit/2a36e08d701c35d826502acc829a90cb4e1043e6 ? I’m not sure if it fully fixes crash in finalizers: -

Some changes have just been added to the origin/next branch! [noreply] MAMA: Added defensive code to mamaMsg_destroy (#264)

Some changes have just been added to the origin/next branch! [noreply] MAMA: Added defensive code to mamaMsg_destroy (#264)

Hi folks, I have just submitted a change which should resolve this issue, but worth a check in your code to verify it has fixed the issue for your use case. It's in the "next" branch. Cheers, Frank

Thanks Aaron, Just on the plugin-only front, I'll probably appreciate more what you mean when a pull request comes in, but it's my opinion that if the plugin code isn't flexible enough to allow us to

Some changes have just been added to the origin/next branch! [noreply] Moved to maven directory structure and added gradle scripts

Some changes have just been added to the origin/next branch! [noreply] Moved to maven directory structure and added gradle scripts

Thanks Aaron, Put in a few changes to the document to make the prototypes "pop" a little bit more. A few suggestions / talking points though: mama_status dqstrategyMamaPlugin_transportPostCreateHook

Thanks Aaron, Apologies for the delay in getting to read this properly - for reference to the group this is the link to the document: https://openmama.github.io/openmama_rfc_source_discovery.html From

Hey, Just to make it easier, here's a direct link to the page: https://openmama.github.io/openmama_rfc_dq_pluggability.html Thanks, Aaron

Hey everyone, You may have noticed that a new RFC has been merged into master of https://github.com/OpenMAMA/openmama.github.io . This is just to make you aware, if you weren’t already. Feel free

Hi Folks, The first version of OpenMAMA’s integration headers was merged into the development branch ready for 2018’s Q1 release last week. For application developers, this effectively

Hi Folks, I have just submitted a batch of changes which introduce OpenMAMA integration headers (so that bridges and plugins can be compiled without requiring access to OpenMAMA’s code matching

Some changes have just been added to the origin/next branch! [noreply] Added public headers for bridge and plugin projects

Some changes have just been added to the origin/next branch! [noreply] Added public headers for bridge and plugin projects

Hi Bill, Sure sounds good, though these are MAMA bridge level configurations so let's make it: mama.middleware.<id>.unload_on_close=true|false and mama.payload.<id>.unload_on_close=true|false Similar

Hi Frank: Why don’t we start over here and see if we can make some progress? If you’re OK with a solution based on a mama.properties setting, I can live with that. For the transport it seems to

I have been quite receptive to your concerns - just not your proposed solution which I think is too coarse. Checking if something exists before trying to access it within a framework is far from a