[ https://issues.apache.org/jira/browse/PROTON-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell reopened PROTON-1096: ------------------------------------ Reopening. While I was expanding the changes proposed in the PR to cover received Deliveries as well, I changed the method signatures from using int to using long so that the 32bit message format would be represented using positive long values only. I have since come to find this causes runtime but not compile time compatibility issues for some of the things out there already using the existing method, so given that I think reverting to use of int as originally present/proposed would be prudent given the limited real world benefit of the alternative. > [proton-j] enable set/get of MessageFormat on the Delivery being > sent/received > ------------------------------------------------------------------------------- > > Key: PROTON-1096 > URL: https://issues.apache.org/jira/browse/PROTON-1096 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-j > Affects Versions: 0.12.0 > Reporter: Sreeram Garlapati > Assignee: Robbie Gemmell > Fix For: 0.12.0 > > Original Estimate: 4h > Remaining Estimate: 4h > > This is a feature request from windows azure eventhubs team. Here's the pull > request: https://github.com/apache/qpid-proton/pull/53 > I (sreeram, from windows azure eventHubs team) am building eventHubs Java > client SDK and taking a dependency on proton-j (which will be available on > GitHub, hopefully, soon) for Amqp. > EventHubs amqp client will need to set a Custom MessageFormat to enable a > Critical scenario for Sending (Send Batch) messages to EventHubs from our > JavaClient. > Delivery class, currently, already has a getMessageFormat().. I extended this > to also have setMessageFormat() method which should be copied to the Transfer > frame. -- This message was sent by Atlassian JIRA (v6.3.4#6332)