-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
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*.
/subsystem=remoting/remote-outbound-connection=remote-ejb-connection:write-attribute(name=protocol, value=) http-remoting https-remoting remote remote+http remote+https
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.
/subsystem=undertow/server=default-server/host=default-host/setting=http-invoker:write-attribute(name=path,value=ejbOverHttp)
- is related to
-
WFLY-13878 Add transformer and subsystem test coverage for EJB over HTTP discovery configuration
-
- Closed
-
-
WEJBHTTP-34 Implement discovery for EJB over HTTP
-
- Resolved
-
-
EJBCLIENT-364 Enable EJB-over-HTTP invocation from standalone client
-
- Resolved
-
-
WFLY-13492 Upgrade Wildfly HTTP Client to 1.1.2.Final
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
