Re: Engine API

On 25 September 2012 21:57, Chuck Rolke cro...@redhat.com wrote: - Original Message - From: Rob Godfrey rob.j.godf...@gmail.com To: proton@qpid.apache.org Sent: Tuesday, September 25, 2012 3:19:23 PM Subject: Re: Engine API On 25 September 2012 19:05, Rafael Schloming r

Re: Proton engine api naming proposal

On 4 October 2012 23:56, Justin Ross jr...@redhat.com wrote: On Wed, 3 Oct 2012, Justin wrote: On Wed, 3 Oct 2012, Rafael Schloming wrote: I believe the convention I'm following is actually the norm (for a good reason). The get/set_foo pattern is used for passive slots, i.e. it's a strong

Re: RC2

As an aside, I have built successfully on Ubuntu 10.10 and 12.04. -- Rob On 24 October 2012 16:49, Rob Godfrey rob.j.godf...@gmail.com wrote: [rob@seelachs ~]$ cmake -version cmake version 2.6-patch 4 On 24 October 2012 16:39, Ken Giusti kgiu...@redhat.com wrote: cmake version 2.6-patch

Re: initial release candidate

My (64-bit) Ubuntu 12.04 works fine... On Ubuntu 10.04 I'm seeing SSL errors... presumably these are related to the age of the ssl library and the algorithms it supports... proton_tests.ssl.SslTest.test_client_authentication

Re: RC3

I got the following failure on proton-c from this release on 32-bit Ubuntu 12.04: proton_tests.codec.DataTest.testDecimal64 fail Error during test: Traceback (most recent call last):

Re: RC5

OK - proton-c built OK for me on Ubuntu 12.04 (32-bit) and Centos 6.3 (32 bit)... Tests all worked fine on the Ubuntu machine. On CentOS I got the following error: proton_tests.messenger.MessengerTest.testSendBogus

Re: [VOTE] 0.2 RC4

[X] Ship it! (Release RC4 as 0.2) Tested java and reviewed C change. -- Rob On 5 November 2012 13:19, Rafael Schloming r...@alum.mit.edu wrote: Posted here: http://people.apache.org/~rhs/qpid-proton-0.2rc4/ [ ] Ship it! (Release RC4 as 0.2) [ ] No (We need another RC because...) The only

Re: inconsistent proton library names?

I've not looked at the branch lately (only just back from vacation), but I would very much hope that there would be nothing preventing having both the JNI and native-Java libraries in the classpath, and allowing for explicit creation of the desired implementation of Connection / Messenger /

Re: mailing lists and fragmented communication

On 21 January 2013 12:43, Robbie Gemmell robbie.gemm...@gmail.com wrote: I'm happy enough with the idea of collapsing proton@ given that Protons scope is in some ways wider than when it started out (where the very specific protocol library made a good case for a separate list), but I don't

Re: Changing the Proton build system to accommodate jni bindings

On 21 January 2013 15:11, Rafael Schloming r...@alum.mit.edu wrote: On Mon, Jan 21, 2013 at 7:10 AM, Rob Godfrey rob.j.godf...@gmail.com wrote: This results in something that is quite awkward for the C build. For one thing I'm not sure an svn export of the proton-c directory

Re: Changing the Proton build system to accommodate jni bindings

On 21 January 2013 18:05, Rafael Schloming r...@alum.mit.edu wrote: On Mon, Jan 21, 2013 at 9:33 AM, Rob Godfrey rob.j.godf...@gmail.com wrote: Ummm... it's a dependency... you're familiar with those, yeah? The same way that the Qpid JMS clients depend on a JMS API jar, for which

Re: Changing the Proton build system to accommodate jni bindings

On 23 January 2013 19:09, Rafael Schloming r...@alum.mit.edu wrote: I've added another wiki page that documents the proton release steps as best I can remember. I'll updated it more during the 0.4 release: https://cwiki.apache.org/confluence/display/qpid/Proton+Release+Steps I think it's

Re: Changing the Proton build system to accommodate jni bindings

Firstly I think it would be helpful if you made clear the requirements you consider to be essential, nice to have, unimportant and/or detrimental. On 23 January 2013 20:17, Rafael Schloming r...@alum.mit.edu wrote: On Wed, Jan 23, 2013 at 8:01 AM, Keith W keith.w...@gmail.com wrote:

Re: Reducing the visibility of proton-j constructors

On 23 January 2013 17:36, Phil Harvey p...@philharveyonline.com wrote: As part of the Proton JNI work, I would like to remove all calls to proton-j implementation constructors from client code. I intend that factories will be used instead [1], thereby abstracting away whether the

Re: Changing the Proton build system to accommodate jni bindings

On 24 January 2013 14:43, Rafael Schloming r...@alum.mit.edu wrote: On Wed, Jan 23, 2013 at 6:10 PM, Rob Godfrey rob.j.godf...@gmail.comwrote: On 23 January 2013 19:09, Rafael Schloming r...@alum.mit.edu wrote: I've added another wiki page that documents the proton release steps as best I

Re: Reducing the visibility of proton-j constructors

, 2013 at 9:39 AM, Rob Godfrey rob.j.godf...@gmail.comwrote: In general dependency on implementation is bad, dependency on interface is better. One of the problems we've had with Qpid historically is it become hard to test as we have dependencies on implementation everywhere. From an end user

Re: Changing the Proton build system to accommodate jni bindings

in this discussion, it is of course important that decisions like this are debated and agreed in public, so rest assured this will all be written up and Jira'd properly so that everyone has the opportunity to comment. Phil On Jan 24, 2013 3:01 PM, Rob Godfrey rob.j.godf...@gmail.com wrote

Re: Parallel Maven and CMake build systems for Proton

A few of supplementary points: 1) The CMake system will not be required to generate pom files or deploy to maven repositories. 2) The CMake system will not be required to perform dynamic dependency resolution 3) The CMake system will not be required to integrate with other build/test tooling

Re: Parallel Maven and CMake build systems for Proton

On 15 February 2013 11:27, Rob Godfrey rob.j.godf...@gmail.com wrote: 2) The CMake system will not be required to perform dynamic dependency resolution I should probably have phrased that one better... What I meant is that (unlike maven) we're not looking for the CMake build to go and find

Re: Testing types in a message

Hi Alan, you can use the java Encoder/Decoders directly like this: import org.apache.qpid.proton.codec.EncoderImpl; import org.apache.qpid.proton.codec.DeccoderImpl; ... ByteBuffer buf = ByteBuffer.allocate(2048); DecoderImpl decoder = new DecoderImpl(); EncoderImpl

Re: Testing types in a message

. -- Rob On 15 February 2013 17:03, Rob Godfrey rob.j.godf...@gmail.com wrote: Hi Alan, you can use the java Encoder/Decoders directly like this: import org.apache.qpid.proton.codec.EncoderImpl; import org.apache.qpid.proton.codec.DeccoderImpl; ... ByteBuffer buf = ByteBuffer.allocate

Re: Testing types in a message

On 15 February 2013 19:17, Alan Conway acon...@redhat.com wrote: On Fri, 2013-02-15 at 17:22 +0100, Rob Godfrey wrote: Of course, if you are using the Message class then there's really no reason to go to the codec directly. you can just use Java Maps/Lists/Arrays etc, along with the Amqp

Re: [RESULT] [VOTE] 0.4 RC3

+1 we should have a tag in the repo for each of our releases -- Rob On 26 February 2013 20:34, Rajith Attapattu rajit...@gmail.com wrote: Rafi, I don't want to sound pedantic, but we should tag our releases as per the guidelines provided by Apache. The previous releases don't have tags

Re: jenkins interop test failing due to PROTON-215 commits?

notificati...@qpid.apache.org -- Rob On 27 February 2013 21:51, Alan Conway acon...@redhat.com wrote: On Wed, 2013-02-27 at 11:19 +, Phil Harvey wrote: Hi, I notice that proton-jni on Jenkins is failing [1] , probably due to the recent PROTON-215 commits. The failing test is:

Re: Need help Re: jenkins interop test failing due to PROTON-215 commits?

On 27 February 2013 23:28, Alan Conway acon...@redhat.com wrote: On Wed, 2013-02-27 at 11:19 +, Phil Harvey wrote: Hi, I notice that proton-jni on Jenkins is failing [1] , probably due to the recent PROTON-215 commits. The failing test is:

Re: can't assign Jira

You should be able to assign JIRAs to yourself now -- Rob On 5 March 2013 16:50, Michael Goulish mgoul...@redhat.com wrote: I created PROTON-260, but I can't seem to assign it to myself. Do I need some new permissions to do this?

Re: put vs. send

On 6 March 2013 13:26, Rafael Schloming r...@alum.mit.edu wrote: On Wed, Mar 6, 2013 at 1:44 AM, Rob Godfrey rob.j.godf...@gmail.com wrote: On 5 March 2013 21:10, Rafael Schloming r...@alum.mit.edu wrote: On Tue, Mar 5, 2013 at 11:24 AM, Ted Ross tr...@redhat.com wrote: [.. snip

Re: put vs. send

Whether that's reported as an error is really a choice of the bindings. In C it's all just return codes. We could add a separate non-blocking flag that causes the blocking operations to return distinct error codes, i.e. the equivalent of EWOULDBLOCK, but I don't think this makes a whole lot

Re: Defining the behaviour of Proton Engine API under error conditions

On 28 March 2013 02:45, Rafael Schloming r...@alum.mit.edu wrote: On Wed, Mar 27, 2013 at 6:34 PM, Rob Godfrey rob.j.godf...@gmail.com wrote: On 27 March 2013 21:16, Rafael Schloming r...@alum.mit.edu wrote: On Wed, Mar 27, 2013 at 11:53 AM, Keith W keith.w...@gmail.com wrote

Re: [VOTE] Subversion to JIRA integration

QPID: Yes [ X ] No [ ] PROTON: Yes [ X ] No [ ] -- Rob On 24 May 2013 13:03, Robbie Gemmell robbie.gemm...@gmail.com wrote: Hi all, As some of you will already know, a mail was sent to committers@a.oearlier outlining some of the newer services ASF infra offer that we may not know about.

Re: QPID Proton SASL header mismatch: 'AMQP\x01\x01\x00\x0a'

Since this looks like an issue you are having with the Qpid C++ broker rather than Proton per se, it's probably worth cross-possting this to the Qpid User list -- Rob On 27 May 2013 18:11, Pablo Rodríguez Rey m...@xkr.es wrote: Thanks Robbie Gemmel, that's what I suspected. I've found the

Re: Data interface in Proton-J

That would be great! Let me have a dig around over the weekend and see if I can find it (I have *lots* of machines where it might be on :-( I should probably be more organised). Cheers, Rob On 14 June 2013 16:01, Leon Mlakar l...@digiverse.si wrote: Hi Rob, thanks for reply. It got me

Re: Data interface in Proton-J

implement them (I think Rafi did tell me once what they are supposed to be for)... But let me first got through the sources and dig through whatever archives I manage to find. Great - just ping me if you have any problems. Cheers, Rob Cheers, Leon On 6/18/13 10:30 AM, Rob Godfrey

Re: Qpid-specific logging facade(s) for Proton etc

So, my main comment would be that I think the Factories should not be depending on the MessageLoggerSpi as you've defined it, but instead purely on EngineLogger. The MessageLogger stuff is a convenience but I don't think it should be mandatory to use it. My other comment would be that I don't

Re: proton-j API factory simplification.

Given the Proton class doesn't require the user to know which implementation they are using (but allows them to explicitly ask for a particular implementation type if they so desire) I'm a little confused how adding the requirement for the user to instantiate an implementation specific class

Re: improving cross language maintainability

On 20 December 2013 19:49, Rafael Schloming r...@alum.mit.edu wrote: On Fri, Dec 20, 2013 at 11:43 AM, Fraser Adams fraser.ad...@blueyonder.co.uk wrote: I've been following this thread with interest and I guess that Rob's comment However I think that would require us to be

Re: AMQP 1.0 session outgoing-window usage / meaning

As far as I can recall/reconstruct the only utility given by the outgoing window was so that the sender (of transfer frames) can indicate to the receiver (of transfer frames) that it will require notification of which frames have been seen by the receiver within window size frames, otherwise the

Re: [VOTE] Release RC 3 as Qpid Proton 0.12.0

To be pedantic, only PMC members votes are officially considered binding [1], and votes from committers who are not on the PMC are not... However in general as a community we would encourage anyone who has done any sort of validation of the release to provide their feedback via (non-binding)

Re: [VOTE] merge the proton mailing list into the users/dev lists

+1 Additionally it might make sense to write a paragraph somewhere on suggestions for best practice on mailing the list (like including components / languages in use in the title or the body of the e-mail :-) ). -- Rob On 30 March 2016 at 11:25, Robbie Gemmell wrote: >

[jira] [Assigned] (PROTON-34) JythonTest.java not executing the jython tests missing

[ https://issues.apache.org/jira/browse/PROTON-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-34: - Assignee: Rob Godfrey JythonTest.java not executing the jython tests missing

[jira] [Resolved] (PROTON-34) JythonTest.java not executing the jython tests missing

[ https://issues.apache.org/jira/browse/PROTON-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-34. --- Resolution: Fixed patch applied JythonTest.java not executing the jython tests

[jira] [Resolved] (PROTON-13) Add JUnit test to proton-j that executes the python unit tests

[ https://issues.apache.org/jira/browse/PROTON-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-13. --- Resolution: Fixed Patch applied Add JUnit test to proton-j that executes the python

[jira] [Commented] (PROTON-21) Extract the logical AMQP frame handling to an AbstractConnectionHandler

[ https://issues.apache.org/jira/browse/PROTON-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13464703#comment-13464703 ] Rob Godfrey commented on PROTON-21: --- I'm holding off on applying this until the work

[jira] [Created] (PROTON-37) Fix failing python tests for Proton-J

Rob Godfrey created PROTON-37: - Summary: Fix failing python tests for Proton-J Key: PROTON-37 URL: https://issues.apache.org/jira/browse/PROTON-37 Project: Qpid Proton Issue Type: Bug

[jira] [Resolved] (PROTON-14) addModified method in ConnectionImpl can cause infinite loop

[ https://issues.apache.org/jira/browse/PROTON-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-14. --- Resolution: Fixed This appears to have been applied addModified method

[jira] [Created] (PROTON-41) Transport tests failing against Proton-j

Rob Godfrey created PROTON-41: - Summary: Transport tests failing against Proton-j Key: PROTON-41 URL: https://issues.apache.org/jira/browse/PROTON-41 Project: Qpid Proton Issue Type: Bug

[jira] [Resolved] (PROTON-41) Transport tests failing against Proton-j

[ https://issues.apache.org/jira/browse/PROTON-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-41. --- Resolution: Fixed Transport tests failing against Proton-j

[jira] [Resolved] (PROTON-42) Maven supriously reporting failure against unit tests

[ https://issues.apache.org/jira/browse/PROTON-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-42. --- Resolution: Fixed Patch applied (magically before it was even posted ;-) ) Maven

[jira] [Assigned] (PROTON-49) Attach frames improperly encoded.

[ https://issues.apache.org/jira/browse/PROTON-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-49: - Assignee: Rob Godfrey Attach frames improperly encoded

[jira] [Created] (PROTON-50) Add accessors for different sections to the Message class

Rob Godfrey created PROTON-50: - Summary: Add accessors for different sections to the Message class Key: PROTON-50 URL: https://issues.apache.org/jira/browse/PROTON-50 Project: Qpid Proton Issue

[jira] [Resolved] (PROTON-50) Add accessors for different sections to the Message class

[ https://issues.apache.org/jira/browse/PROTON-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-50. --- Resolution: Fixed Add accessors for different sections to the Message class

[jira] [Assigned] (PROTON-55) NullPointerException when a Flow is received /w a null delivery count

[ https://issues.apache.org/jira/browse/PROTON-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-55: - Assignee: Rob Godfrey NullPointerException when a Flow is received /w a null delivery count

[jira] [Resolved] (PROTON-55) NullPointerException when a Flow is received /w a null delivery count

[ https://issues.apache.org/jira/browse/PROTON-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-55. --- Resolution: Fixed This should now be fixed - the code was not correctly handling the case where

[jira] [Updated] (PROTON-62) Proton(-j) does not support attaching to the transaction controller

[ https://issues.apache.org/jira/browse/PROTON-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-62: -- Summary: Proton(-j) does not support attaching to the transaction controller (was: ClassCastException

[jira] [Updated] (PROTON-62) Proton(-j) does not support attaching to the transaction coordinator

[ https://issues.apache.org/jira/browse/PROTON-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-62: -- Summary: Proton(-j) does not support attaching to the transaction coordinator (was: Proton(-j) does

[jira] [Commented] (PROTON-65) Provide a AMQP 1.0 Message to JMS Message mapping logic/module

[ https://issues.apache.org/jira/browse/PROTON-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13472673#comment-13472673 ] Rob Godfrey commented on PROTON-65: --- I think it's more of a module/scoping question. I

[jira] [Commented] (PROTON-65) Provide a AMQP 1.0 Message to JMS Message mapping logic/module

[ https://issues.apache.org/jira/browse/PROTON-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13473305#comment-13473305 ] Rob Godfrey commented on PROTON-65: --- I agree that right now we haven't identified

[jira] [Commented] (PROTON-115) Expose API to access link name.

[ https://issues.apache.org/jira/browse/PROTON-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490561#comment-13490561 ] Rob Godfrey commented on PROTON-115: Added getName() to Link in proton-j

[jira] [Updated] (PROTON-115) Expose API to access link name.

[ https://issues.apache.org/jira/browse/PROTON-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-115: --- Fix Version/s: 0.3 Expose API to access link name

[jira] [Assigned] (PROTON-130) Sending pre-settled message results in the TransportSession._outgoingWindowSize going to 0, which stops further transfers.

[ https://issues.apache.org/jira/browse/PROTON-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-130: -- Assignee: Rob Godfrey Sending pre-settled message results in the TransportSession

[jira] [Assigned] (PROTON-84) Disposition sent in response to pre-settled transfer

[ https://issues.apache.org/jira/browse/PROTON-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-84: - Assignee: Rob Godfrey Disposition sent in response to pre-settled transfer

[jira] [Created] (PROTON-132) Unsettled deliveries not being removed from transport session maps

Rob Godfrey created PROTON-132: -- Summary: Unsettled deliveries not being removed from transport session maps Key: PROTON-132 URL: https://issues.apache.org/jira/browse/PROTON-132 Project: Qpid Proton

[jira] [Resolved] (PROTON-132) Unsettled deliveries not being removed from transport session maps

[ https://issues.apache.org/jira/browse/PROTON-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-132. Resolution: Fixed Unsettled deliveries not being removed from transport session maps

[jira] [Assigned] (PROTON-140) [Proton-j] Add contib, examples directories

[ https://issues.apache.org/jira/browse/PROTON-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-140: -- Assignee: Keith Wall [Proton-j] Add contib, examples directories

[jira] [Assigned] (PROTON-138) [proton-j] BufferOverflowException

[ https://issues.apache.org/jira/browse/PROTON-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-138: -- Assignee: Philip Harvey [proton-j] BufferOverflowException

[jira] [Assigned] (PROTON-141) [proton-j] 256K Messages do not get transfered properly

[ https://issues.apache.org/jira/browse/PROTON-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-141: -- Assignee: Rob Godfrey [proton-j] 256K Messages do not get transfered properly

[jira] [Resolved] (PROTON-141) [proton-j] 256K Messages do not get transfered properly

[ https://issues.apache.org/jira/browse/PROTON-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-141. Resolution: Fixed Committed the fix to TransportImpl and the Python test. Omitted the Java test

[jira] [Resolved] (PROTON-146) Simplified CompositeWritableBuffer impl to avoid help buffer overflow exceptions.

[ https://issues.apache.org/jira/browse/PROTON-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-146. Resolution: Fixed Fix Version/s: 0.3 applied patch Simplified

[jira] [Assigned] (PROTON-146) Simplified CompositeWritableBuffer impl to avoid help buffer overflow exceptions.

[ https://issues.apache.org/jira/browse/PROTON-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-146: -- Assignee: Rob Godfrey Simplified CompositeWritableBuffer impl to avoid help buffer

[jira] [Assigned] (PROTON-143) Trace the frame after the onPayloadTooLarge runnable is executed.

[ https://issues.apache.org/jira/browse/PROTON-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-143: -- Assignee: Rob Godfrey Trace the frame after the onPayloadTooLarge runnable is executed

[jira] [Resolved] (PROTON-143) Trace the frame after the onPayloadTooLarge runnable is executed.

[ https://issues.apache.org/jira/browse/PROTON-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-143. Resolution: Fixed Fix Version/s: 0.3 Trace the frame after the onPayloadTooLarge

[jira] [Commented] (PROTON-145) 256K Messages do not get transfered properly with a 64k pump size

[ https://issues.apache.org/jira/browse/PROTON-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500431#comment-13500431 ] Rob Godfrey commented on PROTON-145: Simplified patch applied 256K

[jira] [Created] (PROTON-150) [Proton-J] Surface necessary methods in interface to remove need to cast to Impl

Rob Godfrey created PROTON-150: -- Summary: [Proton-J] Surface necessary methods in interface to remove need to cast to Impl Key: PROTON-150 URL: https://issues.apache.org/jira/browse/PROTON-150 Project

[jira] [Resolved] (PROTON-149) Remove if at TransportImpl.java line 866.

[ https://issues.apache.org/jira/browse/PROTON-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-149. Resolution: Fixed Fix Version/s: 0.3 Remove if at TransportImpl.java line 866

[jira] [Resolved] (PROTON-153) [proton-j] Sender should throw an exception if send is called after the endpoint is locally closed.

[ https://issues.apache.org/jira/browse/PROTON-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-153. Resolution: Fixed Fix Version/s: 0.3 [proton-j] Sender should throw an exception

[jira] [Assigned] (PROTON-153) [proton-j] Sender should throw an exception if send is called after the endpoint is locally closed.

[ https://issues.apache.org/jira/browse/PROTON-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-153: -- Assignee: Rob Godfrey [proton-j] Sender should throw an exception if send is called after

[jira] [Resolved] (PROTON-155) [proton-j] Detach toString() does not include the handle field.

[ https://issues.apache.org/jira/browse/PROTON-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-155. Resolution: Fixed Fix Version/s: 0.3 [proton-j] Detach toString() does not include

[jira] [Assigned] (PROTON-155) [proton-j] Detach toString() does not include the handle field.

[ https://issues.apache.org/jira/browse/PROTON-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-155: -- Assignee: Rob Godfrey [proton-j] Detach toString() does not include the handle field

[jira] [Updated] (PROTON-81) Expose send/receive settle modes

[ https://issues.apache.org/jira/browse/PROTON-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-81: -- Component/s: (was: proton-j) Expose send/receive settle modes

[jira] [Commented] (PROTON-81) Expose send/receive settle modes

[ https://issues.apache.org/jira/browse/PROTON-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507224#comment-13507224 ] Rob Godfrey commented on PROTON-81: --- This was resolved in commits 1399329,1399330

[jira] [Resolved] (PROTON-145) 256K Messages do not get transfered properly with a 64k pump size

[ https://issues.apache.org/jira/browse/PROTON-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-145. Resolution: Fixed Fix Version/s: 0.3 256K Messages do not get transfered properly

[jira] [Resolved] (PROTON-173) Message annotations not properly encoded

[ https://issues.apache.org/jira/browse/PROTON-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-173. Resolution: Fixed Fix Version/s: 0.3 Assignee: Rob Godfrey Patch applied

[jira] [Commented] (PROTON-154) link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach

[ https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507406#comment-13507406 ] Rob Godfrey commented on PROTON-154: I've applied the patch for proton-j

[jira] [Commented] (PROTON-186) Message encode should always return the number of bytes needed to fully encode the message

[ https://issues.apache.org/jira/browse/PROTON-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13531400#comment-13531400 ] Rob Godfrey commented on PROTON-186: Patch applied (with modifications) to add

[jira] [Assigned] (PROTON-127) Rename the org.apache.qpid.proton.type package for nicer Scala support

[ https://issues.apache.org/jira/browse/PROTON-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-127: -- Assignee: Rob Godfrey Rename the org.apache.qpid.proton.type package for nicer Scala

[jira] [Resolved] (PROTON-127) Rename the org.apache.qpid.proton.type package for nicer Scala support

[ https://issues.apache.org/jira/browse/PROTON-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-127. Resolution: Fixed Fix Version/s: 0.3 The type package has been removed. The public API

[jira] [Resolved] (PROTON-156) [proton-j] Detach close field is not being set to true.

[ https://issues.apache.org/jira/browse/PROTON-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-156. Resolution: Fixed Assignee: Rob Godfrey [proton-j] Detach close field is not being set

[jira] [Reopened] (PROTON-219) Move Cmake modules to the tools directory

[ https://issues.apache.org/jira/browse/PROTON-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reopened PROTON-219: The cmake directory (and its sub-sirs) are still present see: svn.apache.org/repos/asf/qpid/proton

[jira] [Updated] (PROTON-60) Support configuring the max frame size.

[ https://issues.apache.org/jira/browse/PROTON-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-60: -- Assignee: Philip Harvey Support configuring the max frame size

[jira] [Updated] (PROTON-60) Support configuring the max frame size.

[ https://issues.apache.org/jira/browse/PROTON-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-60: -- Fix Version/s: 0.4 Support configuring the max frame size

[jira] [Updated] (PROTON-58) NullPointerException on receiver.recv(...)

[ https://issues.apache.org/jira/browse/PROTON-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-58: -- Assignee: Keith Wall NullPointerException on receiver.recv

[jira] [Updated] (PROTON-61) Need a means of specifying and reading connection capabilities properties

[ https://issues.apache.org/jira/browse/PROTON-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-61: -- Fix Version/s: 0.4 Need a means of specifying and reading connection capabilities properties

[jira] [Updated] (PROTON-66) Driver implementation for proton-j

[ https://issues.apache.org/jira/browse/PROTON-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-66: -- Fix Version/s: 0.4 Driver implementation for proton-j

[jira] [Updated] (PROTON-66) Driver implementation for proton-j

[ https://issues.apache.org/jira/browse/PROTON-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-66: -- Assignee: Gordon Sim Driver implementation for proton-j

[jira] [Updated] (PROTON-68) Porting Issue -- dll imports and exports on Visual Studio

[ https://issues.apache.org/jira/browse/PROTON-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-68: -- Fix Version/s: 0.4 Porting Issue -- dll imports and exports on Visual Studio

[jira] [Updated] (PROTON-98) Porting Issue -- Visual Studio compiler requires explicit casts

[ https://issues.apache.org/jira/browse/PROTON-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-98: -- Fix Version/s: 0.4 Porting Issue -- Visual Studio compiler requires explicit casts

[jira] [Updated] (PROTON-99) Porting Issue -- pn_dtag macro does not compile with Visual Studio compiler

[ https://issues.apache.org/jira/browse/PROTON-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-99: -- Fix Version/s: 0.4 Porting Issue -- pn_dtag macro does not compile with Visual Studio compiler

[jira] [Commented] (PROTON-109) Proton should handle inbound max-frame size violations.

[ https://issues.apache.org/jira/browse/PROTON-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13575846#comment-13575846 ] Rob Godfrey commented on PROTON-109: proton-j will also need this change implemented

[jira] [Updated] (PROTON-110) java.lang.NullPointerException: the handle field is mandatory

[ https://issues.apache.org/jira/browse/PROTON-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-110: --- Assignee: Keith Wall java.lang.NullPointerException: the handle field is mandatory

[jira] [Commented] (PROTON-147) Don't send a Sender Disposition until the all the transfers for a delivery have been sent.

[ https://issues.apache.org/jira/browse/PROTON-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13575874#comment-13575874 ] Rob Godfrey commented on PROTON-147: IIRC after discussion I think we concluded

  1   2   >