[jira] Closed: (AXISCPP-685) SSL and non-SSL test suite

["Adrian Dick (JIRA)" <ax...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/AXISCPP-685?page=all ]
     
Adrian Dick closed AXISCPP-685:
-------------------------------

    Resolution: Fixed

You can now include <ssl>true</ssl> within the property file for any given testcase if it requires the SSL library - and this will ensure the appropriate entry is added to the axiscpp.conf file.

I believe this provides the same capability as you were hoping for.

> SSL and non-SSL test suite
> --------------------------
>
>          Key: AXISCPP-685
>          URL: http://issues.apache.org/jira/browse/AXISCPP-685
>      Project: Axis-C++
>         Type: Test
>   Components: Test
>     Versions: current (nightly)
>  Environment: n/a
>     Reporter: Fred Preston
>     Priority: Critical

>
> AXISCPP-684 also raises another, deeper issue.  Currently, the test suite runs with Channel_HTTP_SSL set to the ssl library so all tests will load the SSL library when a web service is created.  This caused a problem with the threading tests because OpenSSL is not multi-threaded.  Also, not everyone wants to use SSL and so what I am proposing is that we have two test suites, one that includes SSL and one that omits SSL.  That is to say, in one test suite we define the Channel_HTTP_SSL attribute in the AXISCPP.CONF file and in the scond test suite, we do not.  This will mean that the SSL specific tests can only be run successfully in the SSL test suite, but this is no bad thing, because there are currently no tests that check what happens when you want to use SSL, but have not defined it in the AXISCPP.CONF file.

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