[jboss-jira] [JBoss JIRA] (WFLY-12190) Reintroduce EJB over HTTP/HTTPS capability with HTTP Loadbalancer - server to server config

[Tomasz Adamski (Jira)]

     [ https://issues.jboss.org/browse/WFLY-12190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomasz Adamski reassigned WFLY-12190:
-------------------------------------

    Assignee: Tomasz Adamski  (was: Flavia Rainone)


> Reintroduce EJB over HTTP/HTTPS capability with HTTP Loadbalancer - server to server config
> -------------------------------------------------------------------------------------------
>
>                 Key: WFLY-12190
>                 URL: https://issues.jboss.org/browse/WFLY-12190
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: EJB
>            Reporter: Brad Maxwell
>            Assignee: Tomasz Adamski
>            Priority: Major
>
> Wildfly/EAP added EJB over HTTP through load balancer, but we missed adding the ability to configure this server to server in the standalone.xml remoting subsystem like the other EJB server to server configs.
> The remoting outbound connection would need an http option , currently it only allows http*-remoting, remote and remote+http*.
> {code}
>  /subsystem=remoting/remote-outbound-connection=remote-ejb-connection:write-attribute(name=protocol,
> value=)
> http-remoting  https-remoting  remote  remote+http  remote+https
> {code}
> Also, Undertow defaults to http://host:8080/wildfly-services for the provider URL to be used, the remote-outbound-configuration for http would need to be able to accept the path, as the path can be configured to a different path from wildfly-services.  It might be good to default to wildfly-services if no path is specified.
> {code}
> /subsystem=undertow/server=default-server/host=default-host/setting=http-invoker:write-attribute(name=path,value=ejbOverHttp)
> {code}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)