You mean interop testing aginst java broker (not client) presumably?
Short guide to getting it running. in /java
mvn
then in /java/distribution
mvn assembly:directory
the in /java/distribution/target/qpid-1.0-incubating-M2-SNAPSHOT-java-bin /qpid-1.0-incubating-M2-SNAPSHOT/bin
export QPID_HOME=`pwd`/.. ./qpid-server
Existing NUnit tests seem happy with their defaults to find that broker running on localhost. If you submit your stuff as a patch, I'll try and get a look at it and get someone here to submit it. Rupert On 1/11/07, Tomas Restrepo <[EMAIL PROTECTED]> wrote:
I've got an initial version of the .NET client authentication support already done. I ended up implementing a simple SASL client (mostly following the SASL Java api documentation and guidelines from http://java.sun.com/j2se/1.5.0/docs/guide/security/sasl/sasl-refguide.html ), and integrating that into the main code base by adding all the necessary support classes and modifying the method handlers as necessary following the original java code (since the API is almost exactly the same, this wasn't a problem). I already got built-in CRAM-MD5, PLAIN and a very rough DIGEST-MD5 mechanism support (though the digest one would never be used as things stand right now). I've got quite a few unit-tests for these and made sure the responses match the rfc samples so I'm hoping they'll work without too much fuss. That said, I haven't been able to do any interop testing against the java client (mostly do to me not being able to run the java client yet; need to solve a couple of environment problems and btw, where the heck is qpid-run supposed to be?), so I would really appreciate it someone could help me out with the testing to ensure the code works as expected. Any takers? Tomas Restrepo [EMAIL PROTECTED] http://www.winterdom.com/weblog/
