[jboss-jira] [JBoss JIRA] Commented: (JBREM-492) would like an API to indicate if a transport requires SSL configuration

[Tom Elrod (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-492?page=comments#action_12339410 ] 
            
Tom  Elrod commented on JBREM-492:
----------------------------------

This has been changed to reside with the TransportClientFactory and TransportServerFactory, which extend ClientFactory and ServerFactory interfaces.  The InvokerRegistry will then load the TransportClientFactory for the transport protocol specified and use that to determine if supports ssl.

The call to the InvokerRegistry.isSSLSupported(String transport) remains the same.

> would like an API to indicate if a transport requires SSL configuration
> -----------------------------------------------------------------------
>
>                 Key: JBREM-492
>                 URL: http://jira.jboss.com/jira/browse/JBREM-492
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.Beta1
>            Reporter: John Mazzitelli
>         Assigned To: Tom  Elrod
>            Priority: Minor
>             Fix For: 2.0.0.CR1 (Boon)
>
>
> Would like an API that I can use where I can give it a transport name (e.g. "http", "sslsocket", etc) and it returns true or false to indicate if its a secure transport and requires SSL configuration? Something like:
> boolean isSecuredBySSL(String transport);
> If you have a remoting app that is running outside of a JBossAS container (and thus don't have the pretty way to configure things with the [mbean] element), but still want to be able to change transports via a configuration file, it would be nice to be able to force a fail-fast configuration error if a secure transport was specified but no SSL configuration properties were specified (for example - if no keystore exists I'd want to fail fast, rather than wait to be told when the connector is started). If this API exists, this would be possible.
> I flagged this with minor priority since you can kinda do this today via "if transport.startsWith("ssl") || transport.equals("https")" but that doesn't take into account any customized transports that are added to the registry during runtime nor does it take into account any new transports that might be added to the remoting core set of transports in the future.
> InvokerRegistry looks like the class that would have this knowledge and would be where such an API lives, but it doesn't have it. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira