[
http://issues.apache.org/jira/browse/GERONIMO-1911?page=comments#action_12376408
]
Vamsavardhana Reddy commented on GERONIMO-1911:
-----------------------------------------------
This part in Geronimo-1911.patch does not make any difference. The part that
is removed and the part that is added are equivalent in functionality.
public void setAlgorithm(String algorithm) {
this.algorithm = algorithm;
- if ("default".equalsIgnoreCase(algorithm)) {
- algorithm = KeyManagerFactory.getDefaultAlgorithm();
- }
- connector.setAttribute("algorithm", algorithm);
+ if ("default".equalsIgnoreCase(algorithm))
+ connector.setAttribute("algorithm",
KeyManagerFactory.getDefaultAlgorithm());
+ else
+ connector.setAttribute("algorithm", this.algorithm);
}
> HTTPS algorithm=Default is not preserved after the server is started
> --------------------------------------------------------------------
>
> Key: GERONIMO-1911
> URL: http://issues.apache.org/jira/browse/GERONIMO-1911
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: Tomcat
> Versions: 1.0, 1.2, 1.1
> Environment: Sun or IBM 1.4.2 JDK
> Reporter: Donald Woods
> Priority: Minor
> Fix For: 1.x
> Attachments: Geronimo-1911.patch
>
> During the first run of the server, the algorithm=Default attribute on the
> TomcatWebSSLConnector in config.xml is updated to match the current JVM being
> used. This causes problems for people switching between Sun and IBM JRE/JDK
> when using Eclipse.
> The fix, is to update HttpsConnectorGBean.java to not set the algorithm
> variable to getDefaultAlgorithm() when "Default" was set, but to just set the
> connector attribute.
--
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
