Remoting WildFly Subsystem Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 4: | Line 4: | ||
=Overview= | =Overview= | ||
==WildFly 9== | |||
<pre> | <pre> | ||
<subsystem xmlns="urn:jboss:domain:remoting:3.0"> | |||
<endpoint worker="default"/> | |||
<http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/> | |||
</subsystem> | |||
</pre> | |||
==EAP 6.4== | |||
<pre> | |||
<subsystem xmlns="urn:jboss:domain:remoting:1.2"> | |||
<connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/> | |||
</subsystem> | |||
</pre> | </pre> | ||
Revision as of 03:26, 7 March 2016
Internal
Overview
WildFly 9
<subsystem xmlns="urn:jboss:domain:remoting:3.0">
<endpoint worker="default"/>
<http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
</subsystem>
EAP 6.4
<subsystem xmlns="urn:jboss:domain:remoting:1.2">
<connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
</subsystem>
Schema
TODO: Link to .xsd.
Configuration Elements
endpoint
The Remoting endpoint uses the XNIO Worker declared and configured by the io subsystem. The XNIO worker's configuration is described here: io subsystem worker configuration.
http-connector
The connector-ref is the name of the Undertow http-listener, so if the name of that connector changes, the Remoting reference should also change.