You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/02/12 11:54:05 UTC
[jira] Created: (QPID-364) AMQMessage and SubscriptionImp
duplicate frame creation code
AMQMessage and SubscriptionImp duplicate frame creation code
-------------------------------------------------------------
Key: QPID-364
URL: https://issues.apache.org/jira/browse/QPID-364
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter: Martin Ritchie
SubscriptionImple has it's own local methods for creating a BasicDeliveryFrame this code is also in AMQMessage. Is there any reason SI needs to contains this logic rather than using AMQMessage?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-364) AMQMessage and SubscriptionImp
duplicate frame creation code
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie resolved QPID-364.
---------------------------------
Resolution: Fixed
This has been resolved by with the introduction of the protocolSession.getProtocolOutputConverter. The SI code now resides there and
the AMQMessage code is commented out.
> AMQMessage and SubscriptionImp duplicate frame creation code
> -------------------------------------------------------------
>
> Key: QPID-364
> URL: https://issues.apache.org/jira/browse/QPID-364
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
>
> SubscriptionImple has it's own local methods for creating a BasicDeliveryFrame this code is also in AMQMessage. Is there any reason SI needs to contains this logic rather than using AMQMessage?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.