[jira] [Commented] (PROTON-642) SASL Servers need to be able to optionally handle clients that don't use SASL

[ https://issues.apache.org/jira/browse/PROTON-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127135#comment-14127135 ] Robbie Gemmell commented on PROTON-642: --- This JIRA only implemented the

[jira] [Updated] (PROTON-665) SASL Servers need to be able to optionally handle clients that don't use SASL

[ https://issues.apache.org/jira/browse/PROTON-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-665: -- Fix Version/s: (was: 0.8) SASL Servers need to be able to optionally handle clients that

[jira] [Resolved] (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 ] Robbie Gemmell resolved PROTON-62. -- Resolution: Fixed I am resolving this JIRA as I believe it was fixed at some point long ago, I

[jira] [Commented] (PROTON-666) TransactionalState applied to indicate the txn-id before sending has no effect on the outgoing transfer frames

[ https://issues.apache.org/jira/browse/PROTON-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127205#comment-14127205 ] ASF subversion and git services commented on PROTON-666: Commit