Hmm ... you certainly should be able to set properties on text messages. If you wouldn't mind, it would help us a lot if you could provide a sample main that demonstrates the problem.
Thanks, Nate On 10/5/07, cmaxo <[EMAIL PROTECTED]> wrote: > > > I'm using the activemq c++ 2.0 client to produce and consume a message to > and > from an activemq 4.1 server. When I produce a message I set a property > like > this: > > textMessage->setStringProperty((const char*)key, (const char*)value); > > where key and value are valid strings and the textMessage variable is a > valid TextMessage. Using wireshark, I see the string properties go to the > mq server as header properties in a tcp packet. > > However, when I read the message and ask for the same property an > exception > is thrown which I catch as a CMSException which indicates: "property not > available in message". I get the text of the message ok but I can never > query for properties. > > My question is what am I doing wrong but along those lines I have a few > others. I'm using the stomp protocol, should I be using another? I'm > using > TextMessages, should I be using ByteMessages? Do I need to setup the > ActiveMQ server with any additional configuration in order to pass those > message properties along? This occurs with any property I try to > set. Any > information or pointer to documentation that explains this is greatly > appreciated. > > Thanks, > Corey > -- > View this message in context: > http://www.nabble.com/activemq-cpp-getStringProperty-tf4576622s2354.html#a13063942 > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > >
