Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

CXF client and server implemented in java or using Spring configuration magically work for this WSDL (under the hood CXF selects correct JMS Conduit and Destination based on address URL).
Details are described in http://cxf.apache.org/docs/jms-transport.html.
CXF also delivers jms_pubsub and jms_pubsub examples illustrating using JMS transport with default settings for ActiveMQ.

...

As far as CXF JMS implementation is Spring based, user can benefit from described Spring JMS functionality.
CXF provides a possibility to configure different Spring aspects in JMS transport using Features. A Feature is something that is able to customize a Server, Client, or Bus, typically adding capabilities. In our case we will add Feature in ws:endpoint and ws:client to tune JMS transport.

...

You can see that endpoint configuration containing JMSConfigFeature feature that has a JMSConfiguration property.
JMSConfiguration supports all settings that we have seen in Spring DefaultMessageListenerContainer: cached connection factory with session pool size, number of concurrent consumers, cache level. All settings of JMSConfiguration are described in details in http://cxf.apache.org/docs/using-the-jmsconfigfeature.html.
Using this configuration server application can be tuned to achieve optimal performance in target environment.

...