Review usage of camel-spring-* modules

[tdiesler]

I think we would like to continue to support camel context deployments through spring XML. This is a widely used method for defining a camel context. Folks might already have camel context definitions in XML and then discover that their app would like to use some middleware functionality that the app server provides (instead of reinventing their own app server). In such cases, it'd be useful if they could easily migrate over to Camel on EAP.

However, these spring descriptors may contain all sorts of non-standard spring provided middleware components, that often enough directly conflict with what EAP provides. JAX-WS is a classic scenario. I'd say, if you run on EAP, your WS endpoint needs to be owed by EAP. Only then you get the benefit of a well integrated WS stack. Security, management, monitoring, clustering, etc. is only available on these EAP WS endpoint - a level of functionality (i.e. added value) that you would not even nearly get when you try to stand up your WS endpoint in any other way.

So ideally, I'd like to take all of these spring components out unless they are direct dependencies of plain vanilla XML based context deployments.

CrossRef: https://issues.redhat.com/browse/FUSEDOC-3642