Hi, I think some of the java test classes use 'testpath' for virtual host and existing examples/docs use that one too.
However, we currently have a virtual host called 'test' defined in the config.xml. I don't have a strong opinion about which we use - but let's pick one. Thoughts ? Thanks, Marnie On 2/6/07, Gordon Sim <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote: > Author: rgreig > Date: Tue Feb 6 03:45:19 2007 > New Revision: 504087 > > URL: http://svn.apache.org/viewvc?view=rev&rev=504087 > Log: > (Submitted by Rupert Smith) Added virtual hosts in order to run tests against Java broker. > > Modified: > incubator/qpid/branches/perftesting_persistent/qpid/cpp/tests/client_test.cpp > incubator/qpid/branches/perftesting_persistent/qpid/cpp/tests/topic_listener.cpp > incubator/qpid/branches/perftesting_persistent/qpid/cpp/tests/topic_publisher.cpp > incubator/qpid/branches/perftesting_persistent/qpid/cpp/tests/topictest I think we should have a default virtual host, that is always available regardless of config (AMQP used to specify one I think, but no longer does). That way the simple case works without messing around with virtual host setup and makes the tests easier to use against different brokers. We could additionally make the vhost settable from the command line if necessary. All we need to agree is what the default is and we can the change the c++ client to use that instead of '/'. BTW, the topictest script seems to have been committed back in DOS format (presumably a result of an erroneous eol style property, I guess we want to set LF on this or at least native?).
