Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-13828

remote+tls is not supported by EJBClient and remote-outbound-connection

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 20.0.1.Final
    • Remoting
    • None

      Hi,

      in our company we would like to use the newest Wildfly together with legacy servers like JBoss AS 7 over SSL.
      This is possible with the Uri scheme "remote+tls" provided by jboss-remoting

      https://github.com/jboss-remoting/jboss-remoting/blob/master/src/main/java/org/jboss/remoting3/EndpointImpl.java

       
final RemoteConnectionProviderFactory remoteConnectionProviderFactory = new RemoteConnectionProviderFactory();
    ...      
 endpoint.addConnectionProvider("remote+tls", remoteConnectionProviderFactory, OptionMap.create(Options.SECURE, Boolean.TRUE));

      But that uri scheme is not supported by the jboss-ejb-client in current version

      https://github.com/wildfly/jboss-ejb-client/blob/master/src/main/java/org/jboss/ejb/protocol/remote/RemoteTransportProvider.java

       public boolean supportsProtocol(final String uriScheme) {
        switch (uriScheme) {
            case "remote":
            case "remote+http":
            case "remote+https":
            // compatibility
            case "remoting":
            case "http-remoting":
            case "https-remoting": {
                return true;
            }
            default: {
                return false;
            }
        }
    }

      and also the remote-outbound-connection does not allow that protocol:
      https://github.com/wildfly/wildfly-core/blob/master/remoting/subsystem/src/main/java/org/jboss/as/remoting/Protocol.java

      public enum Protocol {

    REMOTE("remote"),
    REMOTE_HTTP("remote+http"),
    HTTP_REMOTING("http-remoting"),
    HTTPS_REMOTING("https-remoting"),
    REMOTE_HTTPS("remote+https");

              tadamski@redhat.com Tomasz Adamski
              mgrossmann Matthias Großmann (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: