cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-344) No system test for servlet transport
Date Sat, 03 Oct 2009 17:01:23 GMT

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

Daniel Kulp resolved CXF-344.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 2.1


I'm going to mark this resolved.   Many of the above are already tested in the various servlet
style tests we have.   The rest are pretty much hit with the JAX-WS tck.  If there are specific
issues, new tasks can be created.

> 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.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.


Mime
View raw message