dev@ws-test-harness.java.net

Re: additional client classes not compiled

From: Fabian Ritzmann <Fabian.Ritzmann_at_Sun.COM>
Date: Fri, 02 Nov 2007 20:26:42 +0200

Jitendra Kotamraju wrote:
> 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 ?

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.

> 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)

Will check them out next week. In what repository can I find them?

Fabian