Kenneth L. Hofsass wrote:
> the test harness is getting some development cycles at the moment and
> I wanted to make sure we got your request in. Is there anything else
> you need other than preventing the WSDL from being bundled in the .war
> file?
Great, thanks for asking. This is definitely the most important point.
There would be some more scenarios I'd like to be able to test:
- Support for Provider endpoints. Maybe the test harness can already do
that, I haven't actually looked into it.
- Support to test deployment failures on the server. Right now the only
way you can find out that your service did not deploy is sending a
request and getting back an HTTP 404 error or such. There are many
failure scenarios that are too complicated to test with pure unit tests.
I'd like to be able to deploy the service in the test container and
catch the exception it generates during deployment.
Fabian
> Fabian Ritzmann wrote:
>> Kohsuke Kawaguchi wrote:
>>> Fabian Ritzmann wrote:
>>>> I just started writing an e2e test for WSIT. The test is supposed
>>>> to test whether we are generating the correct WSDL (with policies
>>>> added from wsit.xml) when there is no WSDL bundled with the
>>>> service. It seems to me that the WS test harness is always creating
>>>> WSDL and packaging it with the service? Can that be disabled? If
>>>> no, please consider this a high-priority feature request.
>>>
>>> I guess it was generating WSDL for the purpose of exercising wsgen.
>>>
>>> It's bit tricky to get the local/in-vm transports running correctly
>>> with dynamically generated WSDL, though. I agree that the feature is
>>> needed for exercising more code path, but this is tricky to get right.
>>
>> It's fine to generate the WSDL temporarily, just as long as I can
>> prevent it from being bundled with the final web app.
>>
>> Fabian