Hi I'm looking at the issue to do with the JMS transport strongly depending on Spring. As it happens, JMSConfiguration implements (Spring) InitializingBean for the only purpose of verifying that a connectionFactory has been set.
This causes problems when doing non-Spring CXF deployments. Generally, we should really try to keep the Spring related code in .spring subpackages as it will make it simpler for CXF be integrated with other similar frameworks or deployed in containers providing the optional Spring support only. I'm planning just remove this dependency from the JMSConfiguration so that the JMS transport can be deployed without Spring with 2.2.10. This is really the main property but if it's not been set for some reason in the Spring case then it will be caught anyway. That said, I'll add another check in JMSConfiguration.getOrCreateWrappedConnectionFactory (which by the way attempts to get the connectionFactory from JNDI if it's currently null) to ensure it's been initialized. cheers, Sergey