[
https://issues.apache.org/jira/browse/CXF-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-1891.
------------------------------
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.
> Support multiple data bindings in one service (type-by-type)
> ------------------------------------------------------------
>
> Key: CXF-1891
> URL: https://issues.apache.org/jira/browse/CXF-1891
> Project: CXF
> Issue Type: Wish
> Components: Core
> Affects Versions: 2.1.2
> Reporter: Renaud Denis
> Fix For: Invalid
>
>
> CXF does not seem to support services interfaces declaring a mix of types
> like XFire did. For instance, a service using Aegis databinding should
> support XmlBeans objects as well as aegis-annotated (or XML mapped) POJOs.
> {code:title=Currently Supported}
> public interface MyService {
> void store(Memento memento, String name, String ownerId, boolean
> shared);
> org.w3c.dom.Document listAll();
> }
> {code}
> {code:title=Currently not supported}
> public interface MyService {
> void store(Memento memento, String name, String ownerId, boolean
> shared);
> org.w3c.dom.Document listAll();
> PreferencesDocument retrieve(String leaf, boolean retrieveHierarchy);
> // PreferencesDocument is a org.apache.xmlbeans.XmlObject
> }
> {code}
> XmlBeans/(JAXB?) Integration layers in CXF should provide Aegis Type Creators
> out-of-the-box, at least in order to ensure seamless migration from XFire to
> CXF.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
