Remoting WildFly Subsystem Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 15: | Line 15: | ||
==endpoint== | ==endpoint== | ||
The Remoting endpoint uses the XNIO Worker declared and configured by the [[io WildFly Subsystem|io subsystem]]. The XNIO worker's configuration is described here: [[io WildFly Subsystem Configuration|io subsystem worker configuration]]. | |||
==http-connector== | ==http-connector== | ||
The <tt>connector-ref</tt> is the name of the [[Undertow WildFly Subsystem Configuration#http-listener|Undertow <tt>http-listener</tt>]], so if the name of that connector changes, the Remoting reference should also change. | The <tt>connector-ref</tt> is the name of the [[Undertow WildFly Subsystem Configuration#http-listener|Undertow <tt>http-listener</tt>]], so if the name of that connector changes, the Remoting reference should also change. | ||
Revision as of 03:03, 20 January 2016
Internal
Overview
<subsystem xmlns="urn:jboss:domain:remoting:3.0">
<endpoint/>
<http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
</subsystem>
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.