On 6/15/06, jhakim <[EMAIL PROTECTED]> wrote:
There are a lot of real-world applications that need the ability to send structured data via JMS. For example, take an application that wants to publish a portfolio of bonds (or stocks - take your pick). The logical way to do it would be to have a portfolio container message with zero or more (nested) bond messages. The alternative, breaking a portfolio into a series of bond messages, is VERY cumbersome and requires that the consumer reconstruct the portfolio. This is but one instance of a real-world need to publish arbitrary message structures. Nested MapMessage addresses this need directly and elegantly.
Yes.. but nested Maps also addresses the same issue it seem to me. What does nesting MapMessages buy you that nested Maps do not?
-- View this message in context: http://www.nabble.com/Nested-MapMessage-t1788442.html#a4877171 Sent from the ActiveMQ - Dev forum at Nabble.com.
-- Regards, Hiram Blog: http://hiramchirino.com
