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 2009/02/09 18:02:59 UTC
[jira] Assigned: (QPID-1630) Provide unified message creation
mechanism (MessageFactory)
[ https://issues.apache.org/jira/browse/QPID-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-1630:
------------------------------------
Assignee: Martin Ritchie
> Provide unified message creation mechanism (MessageFactory)
> -----------------------------------------------------------
>
> Key: QPID-1630
> URL: https://issues.apache.org/jira/browse/QPID-1630
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Broker
> Affects Versions: M4
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M5
>
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> Currently, MessageHandleFactory is used to hand out the right handle type. WIth the removal of the MessageHandles this class will be redundant.
> However, a unified point for creating messages and so assigning message IDs would be beneficial.
> Currently the MessageStore is responsible for that task but a MessageFactory would localise that information and make it easier to see how a message is created.
> Currently IncomingMessage and the various MessageStores create the message in two different ways, understandable as one is recovery and one is normal delivery, however, using a MessageFactory would be a cleaner approach and localise the ID generation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org