[
https://issues.apache.org/jira/browse/QPID-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Smith updated QPID-360:
------------------------------
Attachment: Qpid-360.diff
Fixes these problems. Unknown message content type defaults to ByteMessage in
JMS. Unkown destination type defaults to AMQDestination.UNKNOWN_TYPE.
Java Listener can talk to cpp publisher for running client interop tests.
> C++ and Java topic test clients do not talk to each other.
> ----------------------------------------------------------
>
> Key: QPID-360
> URL: https://issues.apache.org/jira/browse/QPID-360
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client, Java Broker, Java Client
> Environment: C++ client, Java client, Java broker, RH Linux.
> Reporter: Rupert Smith
> Attachments: Qpid-360.diff
>
>
> The C++ topictest and Java topictest clients cannot talk to each other as
> they do not communicate on the same topics. It looks as though these clients
> were originally written to be iteroperable but have grown out of synch. They
> need to be altered to cross talk to one another for interop testing.
> I made a few changes to the Java client to bring it into line with the C++.
> There are additional problems because the Java client expects to talk JMS
> messages whereas the C++ is pure AMQP. The Java client needs to be made more
> lax and made to talk pure AMQP. At the moment it null pointers in many places
> where it expects JMS only fileds to be set.
> Would also be nice to have p2p tests. Will create seperate JIRA for that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
