Could you provide a few sniplets of code for how you think API should look?
On 6/14/06, jhakim <[EMAIL PROTECTED]> wrote:
Yes. MapMessage has the same power and flexibility as XML (the universal self-describing data structure) as long as arbitrary nesting is allowed. Take away nesting and MapMessage becomes a very simplistic structure that cannot easily handle real-world application needs. In recognition of this fact, many vendors allow nesting of MapMessage - e.g. TIBCO EMS. Some vendors, such as SonicMQ provide proprietary APIs when it comes to nesting. This, in my opinion, is a very poor design strategy because it binds clients too closely with the vendor API. -- View this message in context: http://www.nabble.com/Nested-MapMessage-t1788442.html#a4873966 Sent from the ActiveMQ - Dev forum at Nabble.com.
-- Regards, Hiram
