Re: Question about proton-c message id API

2013-01-24 Thread Rafael Schloming
On Thu, Jan 24, 2013 at 7:38 AM, Keith W wrote: > On 23 January 2013 15:40, Rafael Schloming wrote: > > Yeah, it appears to be a bug. I checked in a potential fix on trunk. Give > > it a shot and see if it's still an issue. > > > > --Rafael > > Thanks, that has indeed addressed the issue. The M

Re: Question about proton-c message id API

2013-01-24 Thread Keith W
On 23 January 2013 15:40, Rafael Schloming wrote: > Yeah, it appears to be a bug. I checked in a potential fix on trunk. Give > it a shot and see if it's still an issue. > > --Rafael Thanks, that has indeed addressed the issue. The Message system tests which previously failed now run cleanly aga

Re: Question about proton-c message id API

2013-01-23 Thread Rafael Schloming
Yeah, it appears to be a bug. I checked in a potential fix on trunk. Give it a shot and see if it's still an issue. --Rafael On Wed, Jan 23, 2013 at 9:19 AM, Phil Harvey wrote: > I'm working on the proton-c JNI binding and am having trouble with the > Message.getMessageId() JNI implementation. >

Question about proton-c message id API

2013-01-23 Thread Phil Harvey
I'm working on the proton-c JNI binding and am having trouble with the Message.getMessageId() JNI implementation. I am currently calling pn_message_get_id but this is causing a segfault (details below). I suspect that I might be using the proton-c message API incorrectly and would appreciate advi