cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-1891) Support multiple data bindings in one service (type-by-type)
Date Mon, 03 Nov 2008 13:13:44 GMT

    [ https://issues.apache.org/jira/browse/CXF-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644715#action_12644715
] 

Benson Margulies commented on CXF-1891:
---------------------------------------

Some thoughts:

1) The current CXF Aegis is much refactored from XFire. 

2) Integrating XMLBeans with Aegis seems to threaten a sort of cross product of data bindings
with other data bindings. Why stop at Aegis delegating to XMLBeans? What about all the other
combinations? I don't want to be a dog-in-the-design manger here, but having the Aegis binding
grow a series of special cases makes me queasy.

3) It is unfortunate that the CXF community is leaving some XFire users out in the breeze.
However, the community is what it is -- a group of volunteers who apply effort where their
personal and/or professional interests take them. For whatever reason, we've had a history
as follows:

a) Initial pulse of merger activity, including much work from XFire experts.
b) A long period of time in which we didn't hear much from XFire users, and the XFire developers
moved on.
c) A recent set of XFire users attempting migration and running into one thing or another.

Anyhow, I invite you to start a thread on the dev list about all this. No one died and made
me king.




> 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.


Mime
View raw message