Page History

...

CXF clients and servers 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 queue and jms_pubsub examples illustrating using JMS transport with default settings for ActiveMQ.

...

It is possible to achieve scalability of a CXF client and service using Spring JMS functionality and the CXF JMS Configuration Feature.
It is not necessary to write any line of code, just configure and leverage already existing stuff.
Using this feature can have dramatic essential invluence on the performance in for some casesenvironments: in one Prove Of Concept I have improved throughput of the CXF service on 220% throughput on 360% (from 500 to 1800 msg/sec) just using session pool and multithread JMS consumer.!
Generic Reference performance numbers regarding for SOAP over JMS transport are represented in Christian Schneider's article: http://www.liquid-reality.de/pages/viewpage.action?pageId=5865562, so you can easily compare with own results and make appropriate tunning if necessary.

References

1. CXF JMS Transport: http://cxf.apache.org/docs/jms-transport.html
2. CXF Features: http://cxf.apache.org/docs/features.html
3. Spring JMS functionality: http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/jms.html
4. CXF performance: http://www.liquid-reality.de/pages/viewpage.action?pageId=5865562

...