router

Description

Membrane Service Proxy's main object.

The router is a Spring Lifecycle object: It is automatically started and stopped according to the Lifecycle of the Spring Context containing it. In Membrane's standard setup (standalone or in a J2EE web app), Membrane itself controls the creation of the Spring Context and its Lifecycle.

In this case, the router is hot deployable : It can monitor proxies.xml , the Spring configuration file, for changes and reinitialize the Spring Context, when a change is detected. Note that, during the Spring Context restart, the router object itself along with almost all other Membrane objects (interceptors, etc.) will be recreated.

Can be used in

spring:beans, bean

Syntax

					<router 
							exchangeStore="string" 
							hotDeploy="[true,false]"
							adjustHostHeader="[true,false]" 
							indentMessage="[true,false]" 
							adjustContentLength="[true,false]"
							trackExchange="[true,false]" />

Listing 1: router Syntax

Sample

				<beans >
					<router 
							exchangeStore="memoryExchangeStore" 
							adjustHostHeader="true" 
							indentMessage="true" 
							adjustContentLength="true" />
				</beans>

Listing 2: router Example

Attributes

Name	Required	Default	Description
exchangeStore	false	create a {@link LimitedMemoryExchangeStore} limited to the size of 1 MB.	Spring Bean ID of an {@link ExchangeStore}. The exchange store will be used by this router's components ({@link AdminConsoleInterceptor}, {@link ExchangeStoreInterceptor}, etc.) by default, if no other exchange store is explicitly set to be used by them.
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.
jmx	false	-
production	false	false
retryInit	false	false
retryInitInterval	false	5 minutes	number of milliseconds after which reinitialization of <soapProxy>s should be attempted periodically

Child Elements

Position	Cardinality	Element
1	0..1	uriFactory or custom elements
2	0..1	httpClientConfig
3	0..1	transport or custom elements
4	0..*	api, internalProxy, proxy, serviceProxy, soapProxy, sslProxy, stompProxy or swaggerProxy