[
https://issues.apache.org/jira/browse/CXF-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465531
]
willem Jiang commented on CXF-344:
----------------------------------
It is not easy to start up the servlet container in the system test. We need
setup servlet container configuration, generate war , deploy, start up servlet
container and the client.
There are some unit tests which use HTTPUnit in Jax-ws front end for
CXF-servlet test, and we also got the CPI test for servlet run with ant.
> No system test for servlet transport
> ------------------------------------
>
> Key: CXF-344
> URL: https://issues.apache.org/jira/browse/CXF-344
> Project: CXF
> Issue Type: Test
> Components: Transports
> Reporter: Eoghan Glynn
>
> A full system test is requireed for the servlet transport, that should
> include at least the following:
> - deployement into the servlet container (tomcat would probably be the most
> straight-forward to launch from the system test framework)
> - assert that the config (both cxf-servlet.xml and the
> HTTPDestinationConfigBean) is honoured
> - assert that Basic HTTP authentication may be used
> - assert that the expected properties (BASE_PATH, CONTENT_TYPE etc.) are set
> on the incoming message
> - assert that the response to oneways where the implementator fro example
> sleeps for 10 seconds are received by the client *before* the implementor
> returns
> - assert that both decoupled and non-decoupled MEPs are supported
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
