You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Ingo Weiss (JIRA)" <ji...@apache.org> on 2017/07/05 09:22:00 UTC

[jira] [Commented] (ARTEMIS-1267) Avoid certain Map parsings on AMQPMessage

    [ https://issues.apache.org/jira/browse/ARTEMIS-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074474#comment-16074474 ] 

Ingo Weiss commented on ARTEMIS-1267:
-------------------------------------

[~clebert.suconic@jboss.com], mind if I take a look at this?

> Avoid certain Map parsings on AMQPMessage
> -----------------------------------------
>
>                 Key: ARTEMIS-1267
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1267
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: AMQP
>    Affects Versions: 2.1.0
>            Reporter: clebert suconic
>            Assignee: clebert suconic
>            Priority: Blocker
>             Fix For: 2.2.0
>
>
> there are a few map parsers on AMQPMessage that could be avoided... 
> ... we currently parse ApplicationProperties if no Properties are defined.. only to throw it away.
> ... we currently parse MessageAnnotations to throw away also.. because of getAnnotation Properties on Message.type
> We could avoid all that by:
> - reading the ID of the section ahead.
> - using the destination type on the producer instead of the Message.. and only use the message on the case of an anonymous producer.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)