[
https://issues.apache.org/jira/browse/CXF-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644663#action_12644663
]
Renaud Denis commented on CXF-1891:
-----------------------------------
Ok, but for us, this means the freeze of XFire to CXF migration, and I'm afraid
this might be so for a number of people :(
I have the impression this issue does not automatically lead to an overhaul of
the databindings architecture, it's more like _integration of XmlBeans with
Aegis_ than _handling of multiple data bindings_: aegis seems to be able to do
so through the use of type creators...
I think a bunch of code can be retrieved from XFire here... XFire and CXF share
a similar Aegis stack, don't they?
* org.codehaus.xfire.xmlbeans.XmlBeansTypeRegistry
* org.codehaus.xfire.xmlbeans.XmlBeansType
* org.codehaus.xfire.xmlbeans.XmlBeansTypeCreator
* org.apache.cxf.aegis.AegisContext
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
