Hi Mayank,
> a.) Though it working successfully, but at times I see a error as
> "Method Invocation pingPort.ping " even if it injects 'pingPort' as
> port. My understanding is to use the injected port in test.bsh file.
In your tests, anything that fails will fail inside pingPort.ping. So
many different errors will cause that same first line. The other error
output is what's important. Could be that it can't find the SEI. Could
be soap11 vs soap12 envelopes. If you have specific ones that you need
assistance with, go ahead and emiail me the error output.
> b.) At times, I also observe failure in wsdl import when I run xwss/*
> test in a batch. I don't get this error when I run test individually.
> I understand it as an error caused by acquiring and releasing of write
> lock on a few server artifact files.
I don't think I've seen that. Does the test run stop when it has that
problem or does it keep going? Is it over NFS or local filesystem?
What command line are you using to invoke the tests? via ant? or
explicitly with java?
thanks,
Ken
Mayank Mishra wrote:
> Hi Ken,
>
> Thanks a lot for the changes you made. They are running 'successfully'
> now. But yes, I think I have to re-look and make some changes in
> wsit-client.xml.
>
> Also, I have a few basic observations in regard to e2e harness,
>
>
> With Regards,
> Mayank
>
> Ken Hofsass wrote:
>
>> Hi Mayank,
>>
>> I wanted to let you know that I've done my best to update/complete
>> the XWSS tests that you had checked into the e2e harness directory.
>> They all run 'successfully' against a build of the WSIT source tree
>> (from just before the JAXWS 2.1 migration started).
>>
>> If you could review them to make sure they are actually testing what
>> is supposed to be tested, that would be greatly appreciated. For
>> instance, all of the tests have the same wsit-client.xml for
>> instance. All of the endpoints are annotated with
>> BindingType(<soap12>), etc. It made them work, but I'm not sure it's
>> correct.
>>
>> I'd be glad to help answer any questions about what I did or how the
>> harness works.
>>
>> thanks,
>> Ken Hofsass
>>