You are viewing a plain text version of this content. The canonical link for it is here.
Posted to axis-tck@ws.apache.org by Tom Jordahl <to...@macromedia.com> on 2002/09/24 17:03:49 UTC

FW: Classpath problems in jax-rpc tck. . .

This is what our testing engineer had to do to get a number of JAX-RPC TCK tests to pass.

In particular, Sam, we were failing on an enumFloat test with an IllegalArgumentException because the RI generated class was getting used instead of the Axis generated class.  Could this be the root of your automation test failures?

Anyway, Sun should be aware that by default the wrong classes are getting picked up by the tests.
--
Tom Jordahl
Macromedia Server Development


>  -----Original Message-----
> From: 	Alex Glosband  
> Sent:	Tuesday, September 24, 2002 10:39 AM
> To:	Tom Jordahl
> Subject:	Classpath problems in jax-rpc tck. . . 
> 
> I figured out how to get around the classpath problems I was experiencing when running the tck. I didn't know where the classpath was getting set when the individual tests were executing, just knew that the tck classes directory was ending up in the classpath before our classes. Here is where the classpath for the executing tests gets set. This is in the ts.jte file. I just needed to put ${TS_HOME}/classes after ${LOCAL_CLASSES} to get our classes in the classpath first and get the tests to pass.
> 
> ########################################################################
> # Environment ts_unix                                              #
> ########################################################################
> env.ts_unix.description=\
>         Run the runtime tests in a separate JVM (process) on Solaris
> env.ts_unix.menu=true
> env.ts_unix.testsuite=com.sun.ts.lib.harness.TS
> env.ts_unix.command.testExecute=com.sun.ts.lib.harness.ExecTSTestCmd \
>         CLASSPATH=${TS_HOME}/lib/harness.jar:${TS_HOME}/lib/javatest.jar:${TS_HOME}/classes:${JAVA_HOME}/jre/lib/rt.jar:${LOCAL_CLASSES} \
>         DISPLAY=:0.0 \
>         HOME=${user.home} \
>         ${JAVA_HOME}/bin/java ${JAVA_OPTIONS} $testExecuteClass $testExecuteArgs
> 
> ########################################################################
> # Environment ts_win32						       #
> ########################################################################
> env.ts_win32.description=\
>         Run the runtime tests in a separate JVM (process) on Win32
> env.ts_win32.menu=true
> env.ts_win32.testsuite=com.sun.ts.lib.harness.TS
> env.ts_win32.command.testExecute=com.sun.ts.lib.harness.ExecTSTestCmd \
>         CLASSPATH=${TS_HOME}\\lib\\harness.jar;${TS_HOME}\\lib\\javatest.jar;${JAVA_HOME}\\jre\\lib\\rt.jar;${LOCAL_CLASSES};${TS_HOME}\\classes \
> 	windir=${windir} \
> 	SYSTEMROOT=${SYSTEMROOT} \
>         ${JAVA_HOME}\\bin\\java ${JAVA_OPTIONS} $testExecuteClass $testExecuteArgs