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:[EMAIL PROTECTED] Sent: Thursday, June 01, 2006 7:32 AM To: [email protected] 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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/
