Return-Path: Delivered-To: apmail-geronimo-activemq-dev-archive@www.apache.org Received: (qmail 52992 invoked from network); 14 Jun 2006 22:37:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Jun 2006 22:37:31 -0000 Received: (qmail 61355 invoked by uid 500); 14 Jun 2006 22:37:31 -0000 Delivered-To: apmail-geronimo-activemq-dev-archive@geronimo.apache.org Received: (qmail 61330 invoked by uid 500); 14 Jun 2006 22:37:30 -0000 Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-dev@geronimo.apache.org Delivered-To: mailing list activemq-dev@geronimo.apache.org Received: (qmail 61321 invoked by uid 99); 14 Jun 2006 22:37:30 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jun 2006 15:37:30 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of chirino@gmail.com designates 66.249.92.171 as permitted sender) Received: from [66.249.92.171] (HELO ug-out-1314.google.com) (66.249.92.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jun 2006 15:37:30 -0700 Received: by ug-out-1314.google.com with SMTP id m3so611267uge for ; Wed, 14 Jun 2006 15:37:08 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=PrM7BCbIIQJ7InSrPMUkU8KmqVYxRHICWX3CX1VZc1uiyHvKzh4amC9q9XPs46LEZZSAq0QjZL//ArSaSyJNmvAC2i/zKcr/SejsKcB8bv9shmlK7kVzbrqIlOblE1wWZK1TAOiFw1eOWeYtqiYW9jXZ6Bh0Qe1Bay1Sywdnv8Y= Received: by 10.66.216.20 with SMTP id o20mr1127348ugg; Wed, 14 Jun 2006 15:37:08 -0700 (PDT) Received: by 10.66.237.18 with HTTP; Wed, 14 Jun 2006 15:37:08 -0700 (PDT) Message-ID: Date: Wed, 14 Jun 2006 18:37:08 -0400 From: "Hiram Chirino" Sender: chirino@gmail.com To: activemq-dev@geronimo.apache.org Subject: Re: Nested MapMessage In-Reply-To: <4873966.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4872274.post@talk.nabble.com> <4873966.post@talk.nabble.com> X-Google-Sender-Auth: bfacc91090d7a594 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Could you provide a few sniplets of code for how you think API should look? On 6/14/06, jhakim 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