WSRP is integrated into GateIn thanks to the extension mechanism.
The extension artifact defines an extra navigational node, whose page contains the WSRP Admin portlet.
<page-nodes>
<node>
<uri>wsrpConfiguration</uri>
<name>wsrpConfiguration</name>
<label>WSRP</label>
<page-reference>group::/platform/administrators::wsrpConfiguration</page-reference>
</node>
</page-nodes>
As the extension package is deployed, the WSRPServiceIntegration service component is started and that triggers the injection of the WSRP infrastructure (persistent data, web service endpoints, and more) into GateIn.
<component>
<key>org.gatein.integration.wsrp.WSRPServiceIntegration</key>
<type>org.gatein.integration.wsrp.WSRPServiceIntegration</type>
<init-params>
<value-param>
<name>producerConfigLocation</name>
<description>Location of the default producer configuration file</description>
<value>${gatein.conf.dir:classpath:/conf}/wsrp-producer-config.xml</value>
</value-param>
<value-param>
<name>consumersConfigLocation</name>
<description>Location of the default consumers configuration file</description>
<value>${gatein.conf.dir:classpath:/conf}/wsrp-consumers-config.xml</value>
</value-param>
<value-param>
<name>consumersInitDelay</name>
<description>Time (in seconds) after the start of the WSRP extension, waited before the consumers are
started
</description>
<value>2</value>
</value-param>
</init-params>
</component>
producerConfigLocation: The location of the default producer configuration file.
consumersConfigLocation: The location of the default consumers configuration file.
consumersInitDelay: The time period (in seconds) after the start of the WSRP extension, and the consumers must wait before starting. The param is used to ensure that JBoss WS has enough time to publish WSDL before the WSRP Consumer is started.
See also