FYI -- I guess you are using

string& assign ( const char* s );

assign your data with

string& assign ( const char* s, size_t n );

................

string& assign ( const string& str );
string& assign ( const string& str, size_t pos, size_t n );
string& assign ( const char* s, size_t n );
string& assign ( const char* s );
string& assign ( size_t n, char c );
template <class InputIterator>
  string& assign ( InputIterator first, InputIterator last );




Carl Trieloff wrote:

Sorry, I looked in the wrong place.. how do you assign your data to the string object?

Carl.


lroloson wrote:
When I try to specify the length I get an error "error: no matching function for call to
‘qpid::client::Message::setData(std::string, unsigned int)’".

Was the unsigned int parameter implemented after 801239?



Larry Roloson
TRMI Systems Integration

On Oct 20, 2009, at 8:18 AM, Carl Trieloff [via Apache Qpid users] wrote:

lroloson wrote:

I have been successful with messages that are strings, but when
trying to
send binary data, I get the following error;

error: no matching function for call to
‘qpid::client::Message::setData(std::string, unsigned int)’. When
I use the
call the void qpid::client::Message::setData(const std::string&),
the
message is clipped. qpid-tool shows only 2 bytes are queued. I am
using the
cpp direct examples compiled and running in Linux (Revision:
801239).





If your data has /0 in it then you need to specify the 'unsigned int' --
length. Did you do this?

Carl.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[hidden email]



View message @ http://n2.nabble.com/Re-How-to-send-binary-data-in-qpid-tp2597473p3858275.html
To unsubscribe from Re: How to send binary data in qpid, click here.







---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to