Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E21BD10F19 for ; Fri, 27 Sep 2013 14:42:11 +0000 (UTC) Received: (qmail 68506 invoked by uid 500); 27 Sep 2013 14:42:11 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 68435 invoked by uid 500); 27 Sep 2013 14:42:11 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 68427 invoked by uid 99); 27 Sep 2013 14:42:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Sep 2013 14:42:11 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of christian.posta@gmail.com designates 209.85.217.171 as permitted sender) Received: from [209.85.217.171] (HELO mail-lb0-f171.google.com) (209.85.217.171) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Sep 2013 14:42:06 +0000 Received: by mail-lb0-f171.google.com with SMTP id u14so2311771lbd.2 for ; Fri, 27 Sep 2013 07:41:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Moy5Ev2+jkaewpdaLXVD4/XYFxu5p1m12mRjJnJlmx4=; b=oFCo+b5rc0q3+SyIGnY2Gn3Q5SS8D95x4dBybRYb8Rinw0pJ8Y2whUiZs/PevRzHGM 7C0p/9Fa+LSlhaFezQU8Efm3Tc7lGvLWRkkyzDavxAUjOuRiSbwEjANjQZHGxl/J46pg 2a7ioF72viOqXU9LcO6OsaVy+ThjqkFc7AhlGNqDdxYQxEp9k6ulVL2+M7Mi3gbpxGBF 0SvCqnt1W51rjiBQ0cN/ZkEz2+lkEU1siL6dDFLw29vpSVtTI6pw4FgG08NjtmiPrFoS gKvgYJJlBy0uSlWA+fGqX1sLL9JWzr/PfilblKIJg0s90BYB+T4n1jhYx4zsJjntPMgS LLqA== MIME-Version: 1.0 X-Received: by 10.112.155.230 with SMTP id vz6mr2068460lbb.35.1380292905132; Fri, 27 Sep 2013 07:41:45 -0700 (PDT) Received: by 10.114.2.239 with HTTP; Fri, 27 Sep 2013 07:41:45 -0700 (PDT) In-Reply-To: <1380269522660-4671881.post@n4.nabble.com> References: <1380269522660-4671881.post@n4.nabble.com> Date: Fri, 27 Sep 2013 07:41:45 -0700 Message-ID: Subject: Re: JMS activemq protocol conversion that supports the message properties From: Christian Posta To: "users@activemq.apache.org" Content-Type: multipart/alternative; boundary=089e011770cb4be98604e75e7c39 X-Virus-Checked: Checked by ClamAV on apache.org --089e011770cb4be98604e75e7c39 Content-Type: text/plain; charset=ISO-8859-1 Take a look at STOMP protocol. It does a conversion which honors properties in the message. On Fri, Sep 27, 2013 at 1:12 AM, tcarlyle wrote: > We have a software agent that uses JMS to publish messages to an Activemq > topic. Part of the relevant information of those jms messages are set as > "StringProperties" or "IntProperties" in the message by the JMS agent. > > However, I need to subscribe to the activemq topics from Android and there > is no JMS support on Android (as far as I know). I have looked into mqtt > but > the mqtt conversion of JMS messages seems to just pass the message content > itself, not the properties set through "StringProperties" or > "IntProperties". > > From the protocols documentation ( > http://activemq.apache.org/protocols.html) > it is not clear if XMPP or any other protocol implemented on android > supports that. Does anyone know which protocol supports the conversion of > those message properties and how does it convert them? > > Cheers, > Thomas > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/JMS-activemq-protocol-conversion-that-supports-the-message-properties-tp4671881.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta --089e011770cb4be98604e75e7c39--