Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of james.strachan@gmail.com
 designates 66.249.92.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=rSjXp1HYTormsQQtREKzUhjwa+Da6R0k1ZWZWDev8ivVg4kCgHDopbNZc4rkgQtyceI3bDQH5SLQJPyEPHl/8Wlo1ifTuVlOGzAPYfkSvACxw+L97tHTsZcXKPzsIZIy1Hwc2pjs5vC5twhekBILKLFPVe1cLzsyiEkhZt0oCSE=
Message-ID: <ec6e67fd0606050120y1fad49c1jddaf92922623a9eb@mail.gmail.com>
Date: Mon, 5 Jun 2006 09:20:04 +0100
From: "James Strachan" <james.strachan@gmail.com>
To: activemq-users@geronimo.apache.org
Subject: Re: Stomp and TextMessage
In-Reply-To: <af2843cd0606042339y12f0a3b1pa9627886eaa5b7b8@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <7743F17344E95A4CA78A3E53A7AF496B5C2EA8@corpatsmail1.corp.sensis.com>
	 <af2843cd0606042339y12f0a3b1pa9627886eaa5b7b8@mail.gmail.com>

+1

On 6/5/06, Hiram Chirino <hiram@hiramchirino.com> wrote:
> That sounds good to me. +1
>
> On 6/2/06, Mittler, Nathan <nathan.mittler@sensis.com> wrote:
> > So, here's my impression of what we need to do (feel free to make
> > mods)...
> >
> > 1) The stomp transport should always add the content-length header to
> > out-going messages, regardless of content-type or whether or not a
> > content-length was provided on the incoming message.
> > 2) The stomp transport should handle in-coming messages with a
> > content-type header, and should pass that through.
> > 3) If a message comes in without a content-length or a content-type, it
> > should just be assumed a TextMessage.  This way we can use the
> > terminating null character as the delimiter.
> >
> > If we're in agreement as to what needs to be done, I'll capture this in
> > a JIRA issue.
> >
> > Regards,
> > Nate
> >
> > -----Original Message-----
> > From: James Strachan [mailto:james.strachan@gmail.com]
> > Sent: Thursday, June 01, 2006 7:32 AM
> > To: activemq-users@geronimo.apache.org
> > Subject: Re: Stomp and TextMessage
> >
> > Agreed - FWIW we should probably add the content-type handling to
> > Stomp support so folks could explicitly specify its MIME type etc
> >
> > On 5/31/06, Nathan Mittler <nathan.mittler@gmail.com> wrote:
> > > Hi,
> > > I think if you leave off the content-length header, it will be
> > interpreted
> > > as a text message.
> > >
> > > Regards,
> > > Nate
> > >
> > > On 5/31/06, wilkesj <wilkesjoiner@gmail.com> wrote:
> > > >
> > > >
> > > > I'm try to send a TextMessage from a ruby producer to Java consumer.
> > The
> > > > message is being seen as a BytesMessage on the Java side.  I've
> > tried
> > > > setting the type header to TextMessage, javax.jms.TextMessage and
> > > > org.apache.activemq.commands.ActiveMQTextMessage.  How do force it
> > to be a
> > > > TextMessage?
> > > >
> > > > Thanks,
> > > > Wilkes
> > > > --
> > > > View this message in context:
> > > > http://www.nabble.com/Stomp+and+TextMessage-t1712841.html#a4650956
> > > > Sent from the ActiveMQ - User forum at Nabble.com.
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> >
> > James
> > -------
> > http://radio.weblogs.com/0112098/
> >
>
>
> --
> Regards,
> Hiram
>


-- 

James
-------
http://radio.weblogs.com/0112098/