dev@ws-test-harness.java.net

Re: additional client classes not compiled

From: Jitendra Kotamraju <Jitendra.Kotamraju_at_Sun.COM>
Date: Thu, 01 Nov 2007 12:05:53 -0700

Fabian Ritzmann wrote:
> Jitendra Kotamraju wrote:
>> Fabian Ritzmann wrote:
>>> According to the user manual, you just need to drop classes into the
>>> client/ subdirectory and they are compiled and made available to the
>>> client test script. I just tried that and my client class is not
>>> being compiled, let alone used by the test script. I looked around
>>> in the other WSIT e2e test cases and not a single one of them is
>>> using additional Java classes. I guess I ran into a bona fide bug or
>>> is there some undocumented configuration magic?
>> Are you keeping the client classes in "client" dir ?
>
> Definitely, this is my layout:
>
> /
> client /
> MyClass.java
> server /
> MyService.java
> test-descriptor.xml
> test.bsh
>
>
> The test-descriptor.xml looks like this:
>
> <descriptor>
> <description>Test a basic dispatch client without WSIT
> extensions</description>
> <client href ="test.bsh"/>
> <service basedir="./server"/>
> </descriptor>
Is MyClass extending from TestCase ? Everything on your side looks
good. We have few tests that have java based clients. Can you try them ?
(for e.g.: server/misc/client , mtom/tcktest/client etc)

Jitu
>
>
> Fabian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_ws-test-harness.dev.java.net
> For additional commands, e-mail: dev-help_at_ws-test-harness.dev.java.net
>