Chapter 14. Configuring the Endpoints to Load Apache CXF Runtime Configuration
Abstract
Both consumers and providers use the
busCfg attribute to configure the endpoint to load Apache CXF runtime configuration. Its value points to a Apache CXF configuration file.
Important
The Java Business Integration components of Red Hat JBoss Fuse are considered deprecated. You should consider migrating any JBI applications to OSGi.
Specifying the configuration to load
You instruct an endpoint to load Apache CXF runtime configuration using the
busCfg attribute. Both the provider element and the consumer element accept this attribute. The attribute's value is the path to a file containing configuration information used by the Apache CXF runtime. This path is relative to the location of the endpoint's xbean.xml file.
Tip
The Apache CXF configuration file should be stored in the endpoint's service unit.
Each endpoint uses a separate Apache CXF runtime. If your service unit creates multiple endpoints, each endpoint can load its own Apache CXF runtime configuration.
Example
Example 14.1, “Provider Endpoint that Loads Apache CXF Runtime Configuration” shows the configuraiton for a provider endpoint that loads a Apache CXF configuration file called
jms-config.xml.
Example 14.1. Provider Endpoint that Loads Apache CXF Runtime Configuration
<beans xmlns:cxfbc="http://servicemix.apache.org/cxfbc/1.0"
xmlns:greeter="http://cxf.apache.org/jms_greeter"
xmlns:test="http://test">
<cxfbc:provider wsdl="classpath:jms_greeter.wsdl"
service="greeter:JMSGreeterService"
endpoint="GreeterPort"
interfaceName="greeter:JMSGreeterPortType"
useJBIWrapper="false"
busCfg="./jms-config.xml" />
</beans>