[jira] Updated: (CXF-344) No system test for servlet transport

["Dan Diephouse (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Diephouse updated CXF-344:
------------------------------

    Fix Version/s:     (was: 2.0)
                   2.0.1

Rescheduling as we won't be doing this for 2.0 I don't think. 

Just looked at the Servlet code - its pretty bare bones now that we have the AbstractHTTPDestination. Do we still really need something more you think?

> 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
>    Affects Versions: 2.0
>            Reporter: Eoghan Glynn
>            Assignee: willem Jiang
>             Fix For: 2.0.1
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.