[QPID-2776] refactor AMQMessageDelegate(0_8 / 0_10) to rationalise duplicated message property functionality

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: M4, 0.5, 0.6
• Component/s: JMS AMQP 0-x
• Assignee: Unassigned
• Reporter: Robbie Gemmell
• Created: 29/Jul/10 15:18
• Updated: 14/Sep/12 16:02
• Resolved: 14/Sep/12 16:02

Description

AMQMessageDelegate_0_10 and AMQMessageDelegate_0_8 both implement their own property handling. Whilst the underlying data structures are indeed different between the two implementations, there is no need for much of the message property functionality to be duplicated as well like it currently is. This should be refactored such that where appropriate the functionality is provided by the abstract superclass. This will help resolve differences between using the client on varying protocol versions, such as would occur due to the defects shown in QPID-2766 and QPID-2770.

Issue Links

• relates to: QPID-2770 AMQMessageDelegate_0_10 uses Byte.valueOf() when converting String properties to short, int, and long values