[
https://issues.apache.org/jira/browse/CXF-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-716.
-----------------------------
Resolution: Fixed
Fix Version/s: 2.3
We have had tests that test the parsing and processing of the configuration in
http-jetty for a while. Actually bringing up the port and hitting it with
connections and certs and stuff is more of a system test, and we've had sys
tests that test that for a long time as well. I think we're covered.
> Adding the unit test for https in the rt-transport-http-jetty module
> --------------------------------------------------------------------
>
> Key: CXF-716
> URL: https://issues.apache.org/jira/browse/CXF-716
> Project: CXF
> Issue Type: Task
> Components: Transports
> Affects Versions: 2.0
> Reporter: Willem Jiang
> Fix For: 2.3
>
>
> incubator/cxf/trunk/rt/transports/http-jetty/src/test/java/org/apache/cxf/transport/https_jetty/JettySslConnectorFactoryTest.java
> was removed in the CXF-706's patch.
> We need to add a unit test for it.
> Here is some notes of Polar for this test.
> that whole test was not based on giving the connector factory certain
> arguments and getting the
> proper response, it was based on the implementation actually writing to a
> log, and then examining the log.
> Well, this was based on so much of the broken implementation, it was hardly
> worth it to try and devise new means
> for it, and some of it was just plain wrong.
> Like it depended on setting system properties for the JSSE, bad, bad, bad.
> I'll try and think of something to test on it later. I also want to add a
> test so that the configuration is correctly
> read in a unit test instead of just the system tests. But I'll need to
> generate certificates and keystores in
> the unit tests.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
