You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Darryl L. Pierce (JIRA)" <ji...@apache.org> on 2014/02/11 16:17:19 UTC

[jira] [Resolved] (QPID-5546) Perl bindings use encode/decode instead of getContentObject/setContentObject

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

Darryl L. Pierce resolved QPID-5546.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.27

> Perl bindings use encode/decode instead of getContentObject/setContentObject
> ----------------------------------------------------------------------------
>
>                 Key: QPID-5546
>                 URL: https://issues.apache.org/jira/browse/QPID-5546
>             Project: Qpid
>          Issue Type: Bug
>          Components: Perl Client
>            Reporter: Darryl L. Pierce
>            Assignee: Darryl L. Pierce
>             Fix For: 0.27
>
>
> perl qpid client receiving AMQP 1.0 map/list message causes what():  illegal-argument: Not enough data for list, expected 3506438144 bytes but only 254 available (/builddir/build/BUILD/qpid-0.22/cpp/src/qpid/framing/List.cpp:59)
> This defect is similar to bug 1021974. In c++ Vienna client is recommended to use msg.getContenObject() instead of decode(). Current perl client still uses decode() (Message.pm) which causes problems.
> I propose to fix Message.pm to use getContentObject()/setContentObject() instead of encode()/decode() in msg->get_content()/set_content().
> Perl's Message implementation do not have getContentObject()/setContentObject() methods which differentiate from c++ and I also propose to review whether to add those as aliases to get_content/set_content().



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org