[
https://issues.apache.org/jira/browse/CXF-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-863.
-----------------------------
Resolution: Won't Fix
Fix Version/s: Invalid
This improvement request has been open for years and no-one has stepped up to
implement it. As such, it does not seems to be a priority for the existing CXF
community. If, in the future, someone would like to tackle this, feel free to
open is and attach a patch.
> Use CXF namespaces for all features.
> ------------------------------------
>
> Key: CXF-863
> URL: https://issues.apache.org/jira/browse/CXF-863
> Project: CXF
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 2.1
> Reporter: Andrea Smyth
> Fix For: Invalid
>
>
> Child elements of the <jaxws:features
> xmlns:jaxws="http://cxf.apache.org/jaxws> elements must be
> a) custom beans for which the bean class that extends AbstractFeature (like
> <cxf:logging xmlns:cxf="http://cxf.apache.org/core";>)
> b) Spring <bean> elements with a bean class that extends AbstractFeature
> c) Spring <ref> elements referencing a bean whose class extends
> AbstractFeature
> Although b) and c) are supported, the preferred choice is be a) as the whole
> point of the features and custom beans is to hide implementation details such
> as the bean class.
> To allow consistent use of custom beans need to define BeanDefinitionParsers
> for all features. Currently these are missing for
> org.apache.cxf.databinding.stax.StaxDataBindingFeature and
> org.apache.cxf.management.interceptor.ResponseTimeFeature.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
