You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Eoghan Glynn (JIRA)" <ji...@apache.org> on 2007/01/02 16:00:27 UTC
[jira] Created: (CXF-344) No system test for servlet transport
No system test for servlet transport
------------------------------------
Key: CXF-344
URL: http://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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (CXF-344) No system test for servlet transport
Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bozhong Lin reassigned CXF-344:
-------------------------------
Assignee: willem Jiang
> 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
> Assigned To: willem Jiang
>
> 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.
[jira] Commented: (CXF-344) No system test for servlet transport
Posted by "Eoghan Glynn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465729 ]
Eoghan Glynn commented on CXF-344:
----------------------------------
I don't think the CPI test is a good substitute for a system test for a number of reasons:
1. most CXF developers do not run CPI routinely, so this is unlikely to catch a regression until *after* it has been comitted to CXF
2. the CPI test is based on a demo, which is designed to illustrate deployment to a servlet container as *simply* as possible ... a system test on the other hand could assert non-tirvial behaviours & edge cases etc. It was the unnoticed lack of support for a non-default use-case (i.e. decoupled responses) that motivated this JIRA issue in the first place.
In order to simplify running a system test hosted in tomcat, perhaps the Apache Cactus framework (http://jakarta.apache.org/cactus) would be useful?
Alternatively, the HTTPUnit-based test could be extended so that the canned GreeterMessage.xml included a non-anonymous <wsa:ReplyTo> header, and assert that the partial response is sent and that a separate server->client connection is established with the full response. If this approach is taken, this JAX-WS unit test should be promoted to a be a system test (to avoid making the JAX-WS frontend module dependent on WS-A). In fact, the servlet logic will be moving out of the JAX-WS module anyway (see http://issues.apache.org/jira/browse/CXF-342), so this test will have to be moved in any case.
> 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
[jira] Updated: (CXF-344) No system test for servlet transport
Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bozhong Lin updated CXF-344:
----------------------------
Fix Version/s: 2.0
Affects Version/s: 2.0
> 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
> Assigned To: willem Jiang
> Fix For: 2.0
>
>
> 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.
[jira] Updated: (CXF-344) No system test for servlet transport
Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bozhong Lin updated CXF-344:
----------------------------
Fix Version/s: (was: 2.1)
> 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
>
> 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.
[jira] Commented: (CXF-344) No system test for servlet transport
Posted by "willem Jiang (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (CXF-344) No system test for servlet transport
Posted by "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.
[jira] Updated: (CXF-344) No system test for servlet transport
Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bozhong Lin updated CXF-344:
----------------------------
Fix Version/s: (was: 2.0.1)
2.1
pushing this to revisit in 2.1. If it is not necessary, we will close in 2.1
> 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.