[
https://issues.apache.org/jira/browse/PROTON-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107102#comment-15107102
]
ASF subversion and git services commented on PROTON-1096:
---------------------------------------------------------
Commit babdc005adcefc0512403319ee28b8e14c8a6356 in qpid-proton's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=babdc00 ]
PROTON-1096: change the get/set method sigs [back] to use int, avoid a breaking
change for little real world benefit. Mention PR #53 to add reference.
> [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)
