You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Renaud Denis (JIRA)" <ji...@apache.org> on 2008/10/29 10:59:44 UTC
[jira] Updated: (CXF-1891) Aegis DataBinding should support
XmlBeans types
[ https://issues.apache.org/jira/browse/CXF-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Renaud Denis updated CXF-1891:
------------------------------
Description:
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.
was:
CXF does not seems 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.
> Aegis DataBinding should support XmlBeans types
> -----------------------------------------------
>
> Key: CXF-1891
> URL: https://issues.apache.org/jira/browse/CXF-1891
> Project: CXF
> Issue Type: Wish
> Components: Aegis Databinding
> 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.