You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Juan Ramirez (JIRA)" <ji...@apache.org> on 2007/07/27 15:37:18 UTC
[jira] Created: (RIVER-94) remove dependency of SSL provider on
SslEndpoint
remove dependency of SSL provider on SslEndpoint
------------------------------------------------
Key: RIVER-94
URL: https://issues.apache.org/jira/browse/RIVER-94
Project: River
Issue Type: Improvement
Components: com_sun_jini_discovery
Affects Versions: jtsk_2.0
Reporter: Juan Ramirez
Priority: Minor
Bugtraq ID [4893513| http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4893513 ]
The SSL discovery provider currently depends on a back-door interface
(EndpointInternals) to reuse code from SslEndpoint and
SslServerEndpoint. In addition to being hacky, this can cause
problems if the SSL discovery and transport providers are defined in
different class loaders. A cleaner solution would be to refactor commonly
used code in Ssl(Server)Endpoint into a set of com.sun.* library
classes that could then be used by both providers without forcing a
dependency between them. This, however, could impact export approval,
since it makes it easier to modify the behavior of the SSL transport
provider (i.e., by interposing a different implementation of the library
classes).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.