You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rupert Smith (JIRA)" <qp...@incubator.apache.org> on 2007/02/12 14:23:05 UTC
[jira] Updated: (QPID-360) C++ and Java topic test clients do not
talk to each other.
[ 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.
RE: [jira] Updated: (QPID-360) C++ and Java topic test clients do not talk to each other.
Posted by Tomas Restrepo <to...@devdeo.com>.
Alane,
> Glad to see you fixed this, let me know if no-one on the Java side picks
> it up. We really need some automated interop testing between C++ & Java
> projects.
I'd say we need some automated interop testing between all the platforms
supported by the project.
One thing I've noticed that seems to be making this harder than need be (at
least in my dealings with the .NET client and java broker) has been that the
unit tests seem to be a combination of real stand-alone unit tests,
integration tests and advanced integration tests (like failover support)
requiring very specific conditions to be met and special set up.
One thing I'd say would make it easier to automate this would be to
explicitly separate those tests into different suites and also possibly
ensure we had a command line (and even a gui?) client built on top of each
of the different language client code bases so that we can easily run it
against each broker.
I think it would be particularly desirable if all of these integration
clients/tests would be the same set of tests, instead of having each
language implement their own set of tests.
Tomas Restrepo
tomas.restrepo@devdeo.com
http://www.winterdom.com/weblog/
Re: [jira] Updated: (QPID-360) C++ and Java topic test clients do
not talk to each other.
Posted by Alan Conway <ac...@redhat.com>.
On Tue, 2007-02-13 at 08:37 +0000, Marnie McCormack wrote:
> With regard to all the interop suites we need, and the test structure as it
> stands - we need to try and define smaller tasks than we have done (as a
> project) in the past. No-one can realistically (or withouth coercion :-)
> pick up tasks that say such hopeful things as 'change all of xx' or 'do more
> y' :-) Let's try to create more do-able JIRAs and do things in manageable
> chunks.
https://issues.apache.org/jira/browse/QPID-242 is a pretty manageable
chunk that would get us a long way - basically it says we need a set of
standard scripts to run each of the brokers. Then update each project to
run its client tests against each broker.
This only tests a subset (e.g. C++ has a pretty small set of
client-broker tests) but even that will catch a lot of interop nonsense.
Cheers,
Alan.
Re: [jira] Updated: (QPID-360) C++ and Java topic test clients do not talk to each other.
Posted by Marnie McCormack <ma...@googlemail.com>.
Hi All,
Rupert - thanks for your work on the test interop. I wanted to query the
proposal to make the java client test talk more AMQP than JMS. I'm not sure
that this will really represent a more realistic test for users. I think we
need both i.e. tests using JMS messages and tests using non-JMS messages
from java to C++ ?
Let me know what you think - it'd probably be best if I raise a separate
JIRA to detail the set we need for Java to C++ interop.
With regard to all the interop suites we need, and the test structure as it
stands - we need to try and define smaller tasks than we have done (as a
project) in the past. No-one can realistically (or withouth coercion :-)
pick up tasks that say such hopeful things as 'change all of xx' or 'do more
y' :-) Let's try to create more do-able JIRAs and do things in manageable
chunks.
Just my tuppence - hth.
Bfn,
Thanks,
Marnie
On 2/12/07, Tomas Restrepo <to...@devdeo.com> wrote:
>
> Alane,
>
> > Glad to see you fixed this, let me know if no-one on the Java side picks
> > it up. We really need some automated interop testing between C++ & Java
> > projects.
>
> I'd say we need some automated interop testing between all the platforms
> supported by the project.
>
> One thing I've noticed that seems to be making this harder than need be
> (at
> least in my dealings with the .NET client and java broker) has been that
> the
> unit tests seem to be a combination of real stand-alone unit tests,
> integration tests and advanced integration tests (like failover support)
> requiring very specific conditions to be met and special set up.
>
> One thing I'd say would make it easier to automate this would be to
> explicitly separate those tests into different suites and also possibly
> ensure we had a command line (and even a gui?) client built on top of each
> of the different language client code bases so that we can easily run it
> against each broker.
> I think it would be particularly desirable if all of these integration
> clients/tests would be the same set of tests, instead of having each
> language implement their own set of tests.
>
>
> Tomas Restrepo
> tomas.restrepo@devdeo.com
> http://www.winterdom.com/weblog/
>
>
>
>
Re: [jira] Updated: (QPID-360) C++ and Java topic test clients do
not talk to each other.
Posted by Alan Conway <ac...@redhat.com>.
On Mon, 2007-02-12 at 05:23 -0800, Rupert Smith (JIRA) wrote:
> [ 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.
Glad to see you fixed this, let me know if no-one on the Java side picks
it up. We really need some automated interop testing between C++ & Java
projects.
Cheers,
Alan.