no i see on the broker that messages are text by ./bin/activemq browse
for what it's worth i've used iconv object and parsed it directly to
msg.setContentObject. now i make std::string out of it and then feed it to
msg.setContentObject
thank You all for help
--
View this message in context:
ht
dp-Re-qpid-cpp-text-message-tp4699635.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
On 15 July 2015 at 20:51, plsph wrote:
> it was typo during rewrite. broker settings are fine. i don't know what the
> consumer is. i only got producer and broker.
> it's hard to argue with statement that it should work. i've used qpid-proton
> writen in c and i was able to send messages to jms tr
On 07/15/2015 08:51 PM, plsph wrote:
it was typo during rewrite. broker settings are fine. i don't know what the
consumer is. i only got producer and broker.
it's hard to argue with statement that it should work. i've used qpid-proton
writen in c and i was able to send messages to jms transformer
it was typo during rewrite. broker settings are fine. i don't know what the
consumer is. i only got producer and broker.
it's hard to argue with statement that it should work. i've used qpid-proton
writen in c and i was able to send messages to jms transformer and they were
recieved as text message
On 14 July 2015 at 13:52, plsph wrote:
> it still gives BytesMessage
> probably, the problem is with:
>
> If the transformer is set to 'jms', the they type of JMS message will depend
> on the body type of the AMQP message.
>
> Body Type JMS Message Type
> null
it still gives BytesMessage
probably, the problem is with:
If the transformer is set to 'jms', the they type of JMS message will depend
on the body type of the AMQP message.
Body Type JMS Message Type
null Message
Data
On 07/12/2015 08:03 PM, plsph wrote:
it doesn't work with setContentObject, there should be
msg.getContentObject().setEncoding()
but it still doesn't help with my issue.
i use qpid-cpp 0.32, activemq 11.1
code is something like:
Message msg(content);
msg.setContentType() <- i was trying everythi
You dont actually seem to be calling setContentObject at all in the
snippet below, but look to be constructing it with it. Did you try
setting the content using setContentObject instead?
My take from reading previous posts on the subject (such as the one
linked previously, by the person who wrote
it doesn't work with setContentObject, there should be
msg.getContentObject().setEncoding()
but it still doesn't help with my issue.
i use qpid-cpp 0.32, activemq 11.1
code is something like:
Message msg(content);
msg.setContentType() <- i was trying everything, jms-type, text/plain
msg.getContent
On 9 July 2015 at 14:23, Timothy Bish wrote:
> On 07/09/2015 04:40 AM, plsph wrote:
>> hi
>> when sending message by qpid proton writen in c, by default the message is
>> text message and i can recieve it with amqp broker in jms format, but when i
>> try to send message by qpid-cpp library it is a
On 07/09/2015 04:40 AM, plsph wrote:
> hi
> when sending message by qpid proton writen in c, by default the message is
> text message and i can recieve it with amqp broker in jms format, but when i
> try to send message by qpid-cpp library it is always binary message, despite
> message.setcontent("
12 matches
Mail list logo
