Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Message-ID: <779955554.1225274384298.JavaMail.jira@brutus>
Date: Wed, 29 Oct 2008 02:59:44 -0700 (PDT)
From: "Renaud Denis (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Updated: (CXF-1891) Aegis DataBinding should support
 XmlBeans types
In-Reply-To: <187864593.1225274384261.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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