Gordon Sim wrote:
Using 'long strings' only as per your suggestion allows the java clients to at least get through connection with the c++ broker at present (see attached patch; not sure if this will have an impact on JMS compliance). However the topic test still doesn't complete due to use of other non-standard types (in particular the 'binary' type, though I need to do some more investigation into this as the topic test code itself does not seem to set any message properties).
Just to wrap this up, binary property value is the destination url set in BasicMessageConsumer. Robert has I believe checked in (temporary changes to allow the java topic test to run over the c++ broker).
