Syntax

configuration:
  '$ref': <string>
  hotDeploy: <boolean>
  jmxRouterName: <string>
  production: <boolean>
  retryInit: <boolean>
  retryInitInterval: <number>
  uriFactory: {}

configuration:
  '$ref': <string>
  hotDeploy: <boolean>
  jmxRouterName: <string>
  production: <boolean>
  retryInit: <boolean>
  retryInitInterval: <number>
  uriFactory: {}

Attributes

Name	Required	Default	Description	Examples
$ref	false	-	Reference a component defined under components.	-
hotDeploy	false	true	Whether changes to the router's configuration file should automatically trigger a restart. Monitoring the router's configuration file proxies.xml is only possible, if the router is created by a Spring Application Context which supports monitoring. Calling this method does not start or stop the hot deploy feature. It is just for configuration before init is called.	-
jmxRouterName	false	-	Sets the JMX name for this router. Also declare a global <jmxExporter> instance.	-
production	false	false	By default the error messages Membrane sends back to an HTTP client provide information to help the caller find the problem. The caller might even get sensitive information. In production the error messages should not reveal to much details. With this option you can put Membrane in production mode and reduce the amount of information in error messages.	-
retryInit	false	false	Whether the router should continue startup, if initialization of a rule (proxy, serviceProxy or soapProxy) failed (for example, when a WSDL a component depends on could not be downloaded). If false, the router will exit with code -1 just after startup, when the initialization of a rule failed. If true, the router will continue startup, and all rules which could not be initialized will be inactive (=not {@link Proxy#isActive()}). Inactive rules Inactive rules will simply be ignored for routing decisions for incoming requests. This means that requests for inactive rules might be routed using different routes or result in a "400 Bad Request" when no active route could be matched to the request. Once rules become active due to reinitialization, they are considered in future routing decision. Reinitialization Inactive rules may be reinitialized and, if reinitialization succeeds, become active. By default, reinitialization is attempted at regular intervals using a timer (see {@link #setRetryInitInterval(int)}). Additionally, using the {@link AdminConsoleInterceptor}, an admin may trigger reinitialization of inactive rules at any time.	-
retryInitInterval	false	5 minutes	number of milliseconds after which reinitialization of <soapProxy>s should be attempted periodically	-

Child Structure

Element	Cardinality	Description
uriFactory	0..1	Sets the URI factory used by the router. Use this only, if you need to allow special (off-spec) characters in URLs which are not supported by java.net.URI .

Can be used in

No parent elements.