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 much of that client) is
that you should call setContentObject and ensure the encoding of that
value is utf8 using setEncoding("utf8"), which should be sufficient to
make the client emit an AMQP string in the body. Following that, I
don't think you need the setContentType call at all.
Robbie
On 12 July 2015 at 20:03, plsph <gf...@wp.pl> 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.getContentObject().setEncoding()
> sender.send(msg)
>
>
> on the broker site, there is setting:
> <transportConnector name="amqp"
> uri="amqp://0.0.0.0:5672?transport.transformemr=jms"/>
>
> thanks
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/qpid-cpp-text-message-tp4698876p4699111.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
