Kohsuke Kawaguchi wrote:
> Fabian Ritzmann wrote:
>
>> The first issue does not seem to have anything to do with the Java SE
>> endpoint, I can reproduce it with the in-VM transport just as well.
>> When I run this command (similarly to the run-harness target in the
>> build.xml) with Java 5:
>>
>> java -cp build/dist/harness-lib.jar:build/dist/harness.jar WsTest
>> -transport
>> /Users/fr159072/workspace/jax-ws-sources/jaxws-ri/transports/local/build/jaxws-local-transport.jar
>> -cp:wsit-image
>> /Users/fr159072/workspace/wsit_1_0/dist/image/jax-ws-latest-wsit
>> /Users/fr159072/workspace/ws-test-harness/test-harness/test/testcases/wsrm/roundtrip
>>
>
> Note that you shouldn't have to put the harness-lib.jar like that in
> the classpath. You should be able to just do:
>
> java -jar build/dist/harness.jar
>
> I've been using it like that all along. If that doesn't work for you,
> I'd like to know why.
I just added that to the class path without thinking. I will try without
tomorrow.
> First, can you make sure you got the latest harness jar? I vaguely
> recall seeing something similar not so long time ago, and I think I
> fixed that.
I'm working with a clean and up-to-date check out from CVS.
> Otherwise, can you run the harness with the -debug option and send me
> the output? It seems like it's forgetting to pick up some jars.
Will do. I already tried and didn't spot anything suspicious but I'm
sure the output will tell you more than it is telling me.
Fabian