Hi Damian, Just a note: the release subdir is also used by Vlsual Studio for its output, so there will be the rpm scripts and lib/dll/pdb files from the builds. Our Windows git looks like this

Hi Damian, I have our pre-publish check code ready, but it is not pluggable. I’d like to submit it as a patch using #ifdef like the entitlements code. That way I don’t have to maintain it as

Yeah I think something analogous to mamaMsgCallbacks (which should have been called mamaSubscriberCallbacks in hindsight) for the mamaPublisher is the nicest fit here. The advantage of doing it

Folks, Some of you may have noticed a few commits which have just landed in next which relate to the OpenMAMA RPM builds. These are tools which I've been using internally to help facilitate the

Hi Sam (and Glenn) Its interesting to hear the Solace perspective on this. In the RMDS case we are dealing with real messages, they come from the intended destination of the published message (or

Hey Glenn, Tom, I have to agree with Glenn here. I don't think these kind of events belong alongside regular messages, for a couple of reasons. For one, simply enough, they aren't messages. They

Hi Glenn In many cases publishing a message is transactional and can succeed or fail. Failure does not mean that the connection (for the transport or the item is at fault) in which case connection

Hey Reed, This was actually discussed a while ago on the mailing lists, after a question from Guy. At the time Frank responded and indicated that the mamaMsg_freeString function was deprecated and

Hi, Question on mamaMsg_toString & mamaMsg_freeString. toString() calls into bridge impl, but freeString() just returns (is not available in the bridge implmamaPayloadBridgeImpl). Currently

Hi Tom, Sam, Before you responded I was considering the use of an inbox as a solution to Sam’s query but I wasn’t overly keen on it. The reason being that being rejected by the broker felt very

Hi In the Tick42 RMDS bridge we address this problem by allowing applications to use the sendFromInbox methods on a publisher and where applicable converting the an asynchronous response from the

Hey all, We're looking for a way to notify a mama application asynchronously of errors while publishing, specifically when the published message was rejected by the message broker's ACL. Our API

Hi Chad, Thanks for your email. We’ve taken a look at MamaSubscription.java and it does indeed look like there is an issue with the management of the closure when using setupSubscription.

Great. Thanks. For this I was using primarily 64-bit Linux (Fedora 20, x86_64) and that's where I did most of the testing, including the unit testing. On Windows, I did a build for mamda with qpid

Cheers for this Sam. At a quick look the code all looks reasonable. Have you performed any testing around the changes? It seems like a good candidate for some unit tests - most likely within the

Hey, Here is a patch that adds wombatQueue_deallocate, which makes it possible to reclaim resources if wombatQueue_create fails. Cheers, Sam diff --git a/common/c_cpp/src/c/queue.c

Awesome, looks really great Alireza. I'll take a look through the patches attached to the Bugzilla and provide any feedback there. Obviously you've put a lot of effort into the testing here, really

Hey Sam, Personally I would be inclined towards the addition of wombatQueue_deallocate, and then having this called within the context of the existing wombatQueue_destroy. This would result in no

Thanks Chad, we'll take a look. D

Hi Damian, I have attached a patch in the bugzilla ticket containing a new JUnit test case for testing the new create method. Regards, Chad Meyer|Corporate & Investment Bank | PIM Market