[ http://issues.apache.org/jira/browse/AXISCPP-742?page=all ]
Fred Preston closed AXISCPP-742:
--------------------------------
Resolution: Fixed
There is now more value checking on each parameter. This will not trap all
incorrect information, but should now report when the wrong type of values has
been used...
> Passing the wrong information to SetSecure() causes and exception
> -----------------------------------------------------------------
>
> Key: AXISCPP-742
> URL: http://issues.apache.org/jira/browse/AXISCPP-742
> Project: Axis-C++
> Type: Improvement
> Components: Transport (axis3), Transport (Client)
> Versions: current (nightly)
> Environment: n/a
> Reporter: Fred Preston
> Assignee: Fred Preston
> Priority: Minor
>
> When using security, if one of the parameters passed to SetSecure is
> incorrect, in the web service stub, then when includeSecure is called, the
> contents of the parameters passed is not checked properly and can lead to an
> exception being thrown. This is esp true for the first parameter. If
> possible, when the SSL is loaded and this filename used, can we check that
> SSL was loaded correctly before continuing with the configuration (if the
> filename should have an extension of xyz, but is passed one with abc).
--
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
