Fabian Ritzmann wrote:
> Jitendra Kotamraju wrote:
>>> No, it's extending an abstract base class from JAX-WS. According to
>>> the user manual, you can drop arbitrary Java code into the client dir.
>> No, it has to be a junit testcase. If the doc is incorrect, we should
>> update it.
>
> Ouch, that explains it all. I believe I remember the wrong piece of
> documentation, I'll try to fix it some time.
I replaced these instructions:
If your client test scripts need some Java helper code (such as
handlers), or if you have some JUnit test classes written as Java
classes, you can put them under the testdir/client directory. All
classes that ends with "Test" will be considered JUnit tests and
executed like client test scripts.
Also, all the Java source files are compiled and made available to
client test scripts (for example so that you can access those classes.)
The "client" package itself will be also imported into the client test
scripts, so classes in the "client" package can be accessed by their
short name.
by this:
Instead of client test scripts, you can use JUnit test classes
implemented as Java classes. Put the source code under the
testdir/client directory. All classes that end with "Test" will be
considered JUnit tests and executed like client test scripts.
Fabian