[GitHub] qpid-proton pull request: support one or more data sections in amq...

2016-01-13 Thread SreeramGarlapati 
GitHub user SreeramGarlapati opened a pull request:

https://github.com/apache/qpid-proton/pull/54

support one or more data sections in amqpMessage

This is a suggestion on how to implement the feature request PROTON-1098 
and is NOT COMPLETE, although, the code works (while sending the message - I am 
able to send an AmqpMessage with Multiple Data sections using this 
implementation).

Usage:
While sending a Message, instead of creating the message with Data section, 
the following can be done:
Message amqpMessage = Proton.message();
amqpMessage.setBody(new DataList(dataList))

(tagging the proton-j expert: @gemmellr to do the needful)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/SreeramGarlapati/qpid-proton 
amqpMsg.supportOneOrMoreDataSections

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-proton/pull/54.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #54


commit 76559ad506e1c26aed98cadd601ddb56899607fe
Author: Sreeram Garlapati 
Date:   2016-01-13T18:05:45Z

proton-j: Support one or more Data sections in AmqpMessage

commit b6de9ba02819492a802211d80ce0acd2e3f2f3cb
Author: Sreeram Garlapati 
Date:   2016-01-13T18:06:15Z

proton-j: Support one or more Data sections in AmqpMessage




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (PROTON-1098) Add support for one or More Data Sections in AmqpMessage

2016-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096723#comment-15096723
 ] 

ASF GitHub Bot commented on PROTON-1098:


GitHub user SreeramGarlapati opened a pull request:

https://github.com/apache/qpid-proton/pull/54

support one or more data sections in amqpMessage

This is a suggestion on how to implement the feature request PROTON-1098 
and is NOT COMPLETE, although, the code works (while sending the message - I am 
able to send an AmqpMessage with Multiple Data sections using this 
implementation).

Usage:
While sending a Message, instead of creating the message with Data section, 
the following can be done:
Message amqpMessage = Proton.message();
amqpMessage.setBody(new DataList(dataList))

(tagging the proton-j expert: @gemmellr to do the needful)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/SreeramGarlapati/qpid-proton 
amqpMsg.supportOneOrMoreDataSections

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-proton/pull/54.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #54


commit 76559ad506e1c26aed98cadd601ddb56899607fe
Author: Sreeram Garlapati 
Date:   2016-01-13T18:05:45Z

proton-j: Support one or more Data sections in AmqpMessage

commit b6de9ba02819492a802211d80ce0acd2e3f2f3cb
Author: Sreeram Garlapati 
Date:   2016-01-13T18:06:15Z

proton-j: Support one or more Data sections in AmqpMessage




> Add support for one or More Data Sections in AmqpMessage
> 
>
> Key: PROTON-1098
> URL: https://issues.apache.org/jira/browse/PROTON-1098
> Project: Qpid Proton
>  Issue Type: New Feature
>  Components: proton-j
>Affects Versions: 0.12.0
>Reporter: Sreeram Garlapati
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> As per Amqp 1.0 spec: 
> http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf, 
> AmqpMessage MessageFormat:0 should allow having one or more data sections. 
> Reference from the Spec:
> "Thebodyconsistsofoneofthefollowingthreechoices: 
> oneormoredatasections,oneormoreamqp-sequence sections, or a single amqp-value 
> section".
> This is a feature request from Windows Azure EventHubs team. This is heavily 
> used for enabling critical scenarios. I deeply Appreciate your help here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (PROTON-1086) Release 11.1 and following versions on PyPI

2016-01-13 Thread Ken Giusti (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Giusti resolved PROTON-1086.

   Resolution: Fixed
Fix Version/s: 0.11.1

0.11.1 is now available on pypi

> Release 11.1 and following versions on PyPI
> ---
>
> Key: PROTON-1086
> URL: https://issues.apache.org/jira/browse/PROTON-1086
> Project: Qpid Proton
>  Issue Type: Wish
>  Components: python-binding
>Affects Versions: 0.11.0
> Environment: https://pypi.python.org/pypi
>Reporter: Javier Ruere
>Assignee: Ken Giusti
> Fix For: 0.11.1
>
>
> Versions after 10.0 do not show up in PyPI.
> It would be very convenient if the packages were published there like it was 
> done with version 10.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (PROTON-1099) Upload latest stable release of python-qpid-proton onto pypi

2016-01-13 Thread Ken Giusti (JIRA) 
Ken Giusti created PROTON-1099:
--

 Summary: Upload latest stable release of python-qpid-proton onto 
pypi
 Key: PROTON-1099
 URL: https://issues.apache.org/jira/browse/PROTON-1099
 Project: Qpid Proton
  Issue Type: Task
  Components: python-binding
Affects Versions: 0.12.0
Reporter: Ken Giusti
Assignee: Ken Giusti
Priority: Blocker
 Fix For: 0.12.0


A reminder to update Pypi when a new release of proton is available.

I'll move the fix version forward as releases are completed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (PROTON-1086) Release 11.1 and following versions on PyPI

2016-01-13 Thread Javier Ruere (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097433#comment-15097433
 ] 

Javier Ruere commented on PROTON-1086:
--

Thanks!

> Release 11.1 and following versions on PyPI
> ---
>
> Key: PROTON-1086
> URL: https://issues.apache.org/jira/browse/PROTON-1086
> Project: Qpid Proton
>  Issue Type: Wish
>  Components: python-binding
>Affects Versions: 0.11.0
> Environment: https://pypi.python.org/pypi
>Reporter: Javier Ruere
>Assignee: Ken Giusti
> Fix For: 0.11.1
>
>
> Versions after 10.0 do not show up in PyPI.
> It would be very convenient if the packages were published there like it was 
> done with version 10.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Proton 0.12.0 release update - Alpha is available

2016-01-13 Thread Justin Ross 
Hello, everyone.  It's time for the Proton 0.12.0 alpha.

  Revision: 576f656b on master
  Artifacts:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.0-alpha/
  Test output:
http://people.apache.org/~jross/qpid-releases/quirk-proton-0.12.0-alpha.log

See the release page[1] for more information about the schedule and
criteria for accepting changes.

We branch for release in *one week*.  Start your testing early.

Thanks!
Justin

---
[1] Proton 0.12.0 release page:
https://cwiki.apache.org/confluence/display/qpid/Qpid+Proton+0.12.0

[jira] [Resolved] (PROTON-1096) [proton-j] enable set/get of MessageFormat on the Delivery being sent/received

2016-01-13 Thread Robbie Gemmell (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved PROTON-1096.

   Resolution: Fixed
Fix Version/s: 0.12.0

> [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)

[jira] [Commented] (PROTON-1096) [proton-j] enable set/get of MessageFormat on the Delivery being sent/received

2016-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096409#comment-15096409
 ] 

ASF GitHub Bot commented on PROTON-1096:


Github user gemmellr commented on the pull request:

https://github.com/apache/qpid-proton/pull/53#issuecomment-171342712
  
Hi Sreeram,

I have made some changes that should let you do what you want. They change 
the API a little by usling a long to make it more intuitive (the message-format 
field is an unsigned int) and also implement the incoming side so that 
[proton-j] recievers can inspect the value should it have been adjusted.

Robbie

As an aside, some hints/tips regarding the Apache<->GitHub integration:

If you create a JIRA before the pull request and include the JIRA key in 
the PR title then a bot will update the JIRA with notice of creation of the PR, 
and also seperately for any comments made on the PR.

If you also include the JIRA key in any commits, then if they are merged 
as-is their details will be added as a comment on JIRA when pushed to the ASF 
repo, helping keep the details together for later reference.

For example, see #6 and its associated JIRA PROTON 814 (missed out the dash 
to avoid it being updated).

(mentioning PROTON-1096 here to have the bot update it too)


> [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)

[jira] [Created] (PROTON-1097) [proton-j] validate details for message-format value on received transfers

2016-01-13 Thread Robbie Gemmell (JIRA) 
Robbie Gemmell created PROTON-1097:
--

 Summary: [proton-j] validate details for message-format value on 
received transfers
 Key: PROTON-1097
 URL: https://issues.apache.org/jira/browse/PROTON-1097
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-j
Affects Versions: 0.12.0
Reporter: Robbie Gemmell
Priority: Minor


The spec \[1\]  notes various details for the message-format field which we 
dont currently enforce, such as that it must be present on the first transfer 
of a multi-transfer message, can be omitted on continuations, and that [if set] 
it is an error for the format on a contituation to differ from the first 
transfer.

Previously the format was alwayss et to 0 on outgoing transfers, and never 
used/inspected at all on incoming transfers, with the 
Delivery#getMessageFormat() method always returning 0. Following PROTON-1096, 
the value on the first transfer for a message is used to update the 
message-format value returned from the Delivery object.

\[1\] 
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-transfer



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (PROTON-1096) [proton-j] enable set/get of MessageFormat on the Delivery being sent/received

2016-01-13 Thread Robbie Gemmell (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated PROTON-1096:
---
Summary: [proton-j] enable set/get of MessageFormat on the Delivery being 
sent/received   (was: ability to specify MessageFormat on Transfer frame while 
sending)

> [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
>   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)

[jira] [Updated] (PROTON-1038) message-format on received transfer is never checked (nor made available for application to check)

2016-01-13 Thread Robbie Gemmell (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated PROTON-1038:
---
Description: Removing proton-j from the component list here and splitting 
it out to its own JIRAs, PROTON-1096 and PROTON-1097.
Component/s: (was: proton-j)

> message-format on received transfer is never checked (nor made available for 
> application to check)
> --
>
> Key: PROTON-1038
> URL: https://issues.apache.org/jira/browse/PROTON-1038
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.11.0
>Reporter: Gordon Sim
>Priority: Minor
>
> Removing proton-j from the component list here and splitting it out to its 
> own JIRAs, PROTON-1096 and PROTON-1097.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (PROTON-1096) ability to specify MessageFormat on Transfer frame while sending

2016-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096342#comment-15096342
 ] 

ASF GitHub Bot commented on PROTON-1096:


Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton/pull/53


> ability to specify MessageFormat on Transfer frame while sending
> 
>
> 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
>   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)

[jira] [Assigned] (PROTON-1096) [proton-j] enable set/get of MessageFormat on the Delivery being sent/received

2016-01-13 Thread Robbie Gemmell (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell reassigned PROTON-1096:
--

Assignee: Robbie Gemmell

> [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
>   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)

[GitHub] qpid-proton pull request: [PROTON-1096]: expose seting MessageForm...

2016-01-13 Thread gemmellr 
Github user gemmellr commented on the pull request:

https://github.com/apache/qpid-proton/pull/53#issuecomment-171342712
  
Hi Sreeram,

I have made some changes that should let you do what you want. They change 
the API a little by usling a long to make it more intuitive (the message-format 
field is an unsigned int) and also implement the incoming side so that 
[proton-j] recievers can inspect the value should it have been adjusted.

Robbie

As an aside, some hints/tips regarding the Apache<->GitHub integration:

If you create a JIRA before the pull request and include the JIRA key in 
the PR title then a bot will update the JIRA with notice of creation of the PR, 
and also seperately for any comments made on the PR.

If you also include the JIRA key in any commits, then if they are merged 
as-is their details will be added as a comment on JIRA when pushed to the ASF 
repo, helping keep the details together for later reference.

For example, see #6 and its associated JIRA PROTON 814 (missed out the dash 
to avoid it being updated).

(mentioning PROTON-1096 here to have the bot update it too)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] qpid-proton pull request: [PROTON-1096]: expose seting MessageForm...

2016-01-13 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton/pull/53


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (PROTON-1096) ability to specify MessageFormat on Transfer frame while sending

2016-01-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096341#comment-15096341
 ] 

ASF subversion and git services commented on PROTON-1096:
-

Commit 01479895895d6b1b33f04dc89ff19fd415202d72 in qpid-proton's branch 
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=0147989 ]

PROTON-1096: enable adjusting the Delivery message format as used on outgoing 
transfers, and retrieving the value for an arriving Delivery

This closes #53


> ability to specify MessageFormat on Transfer frame while sending
> 
>
> 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
>   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)

[jira] [Commented] (PROTON-1096) [proton-j] enable set/get of MessageFormat on the Delivery being sent/received

2016-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096525#comment-15096525
 ] 

ASF GitHub Bot commented on PROTON-1096:


Github user SreeramGarlapati commented on the pull request:

https://github.com/apache/qpid-proton/pull/53#issuecomment-171362388
  
Awesome! Thanks a lot Robbie.
Details about JIRA integration is helpful. Thanks!


> [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)

[GitHub] qpid-proton pull request: [PROTON-1096]: expose seting MessageForm...

2016-01-13 Thread SreeramGarlapati 
Github user SreeramGarlapati commented on the pull request:

https://github.com/apache/qpid-proton/pull/53#issuecomment-171362388
  
Awesome! Thanks a lot Robbie.
Details about JIRA integration is helpful. Thanks!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---