CXF configuration ideasPage added by Christian SchneiderEnvironmentCXF is intended to work in a wide range of containers / frameworks:
It for each of the important cases it should be as easy and natural to configure CXF for the developer. Problem descriptionCurrently CXF provides a lot of integration points with frameworks as well as CXF proprietary ways of configuration. Out current approach has several drawbacks:
IdeaThe general idea is to step back and keep injection out of CXF as much as possible and instead rely more on the frameworks to do this job. This should make CXF much more embedable and less complex. We still can have some glue code for the frameworks but at as few points as possible. A good example for this is camel which defines a registry concept that is implemented differently for each framework. In spring it relies on the spring context in blueprint on the blueprint context, in OSGi on services. The camel registry is not perfect but a good step in the right direction. In the following checpters we should look into the respective frameworks and discuss how CXF integration should work ideally. SpringXMLAnnotation basedBlueprintCDIEndpoint
Stop watching space
|
Change email notification preferences
View Online
|
[CONF] Apache CXF > CXF configuration ideas
Christian Schneider (Confluence) Tue, 10 Dec 2013 01:07:57 -0800
- [CONF] Apache CXF > CXF configuration ... Christian Schneider (Confluence)
- [CONF] Apache CXF > CXF configura... Christian Schneider (Confluence)
- [CONF] Apache CXF > CXF configura... Christian Schneider (Confluence)