On 13/06/07, Rajith Attapattu <[EMAIL PROTECTED]> wrote:
As I mentioned, any important modifications/improvements should be
accomadated in the new client where is makes sense.
Some of these changes might not be applicable due to protocol
changes/improvements and/or new client architecture.
Yeah, some work-around stuff will be dropped because it won't be needed for
the new protocol.
[RA] It's a reasonable request. How are u guys supporting it currently? Are
u using a retrotranslator jars?
We're using the retrotranslator, which has a maven plugin from the codehaus
mojo project. There is a working example in the existing client/pom.xml,
that can be copied accross. There is also a client-java14 package, which
exists to re-pacakge the client for 1.4 and to run its tests under 1.4. Also
common and integrationtests are also retrotranslated.
To turn on retrotranslator verification you need to add some properties, for
example to a profile in your maven settings.xml. Here's an example from
mine:
<profile>
<id>inject-properties-qpid</id>
<properties>
<!-- No python tests. -->
<skip.python.tests>true</skip.python.tests>
<!-- Configure log4j stuff. -->
<log4j.configuration
file:/c:/home/rupert/qpid/trunk/qpid/java/etc/mylog4j.xml</log4j.configuration>
<log4j.perftests
file:/c:/home/rupert/qpid/trunk/qpid/java/etc/mylog4j.xml</log4j.perftests>
<!-- Configure retrotranslator verification stuff. -->
<retrotranslator.verify>true</retrotranslator.verify>
<retrotranslator.1.4-rt-path>c:/Program
Files/Java/j2re1.4.2_12/lib/rt.jar</retrotranslator.1.4-rt-path>
<retrotranslator.1.4-jce-path>c:/Program
Files/Java/j2re1.4.2_12/lib/jce.jar</retrotranslator.1.4-jce-path>
<retrotranslator.1.4-jsse-path>c:/Program
Files/Java/j2re1.4.2_12/lib/jsse.jar</retrotranslator.1.4-jsse-path>
<retrotranslator.1.4-sasl-path>c:/Program
Files/Java/j2re1.4.2_12/lib/ext/sasl.jar</retrotranslator.1.4-sasl-path>
<!-- Configure 1.4 jvm location for testing 1.4 client
builds. -->
<!--<jvm.1.4.bin>c:/Program
Files/Java/j2re1.4.2_12/bin/java.exe</jvm.1.4.bin>-->
</properties>
</profile>
The systests/integrationtests modules are a little confusing because at
first it seems they should be the same thing. The intention is that systests
contains non-unit tests, where java client is run against the java broker
(could be in-vm or standalone broker). The test the java client/broker
together as a system. Integration tests, tests the java client through *any*
broker. They tests its integration with the Qpid Java broker or other
products; the interop tests are in this module.
You are right, in that some stuff does need to be moved out of
client/src/tests into systests.
Rupert
