Yes the reason for this is that our primary clients are mobile devices, some of which have very limited XML parsing capabilities. REST seems to emphasize simplicity and namespace handling is not always simple. SOAP is a little too 2009 for my taste. :-)
-----Original Message----- From: Benson Margulies [mailto:[email protected]] Sent: Tuesday, September 28, 2010 9:09 PM To: [email protected] Subject: Re: Aegis Binding without namespaces It's a big problem. The mapping of packages to namespaces avoids collisions. If you don't want namespaces, then you have to find another solution. I personally find no-namespace XML to be entirely too 1999 for my taste, but I imagine that you have a good reason for it. On Tue, Sep 28, 2010 at 4:49 PM, Daniel Kulp <[email protected]> wrote: > > I honestly don't think anyone has looked at this at all. If it's something > you need, you'll likely have to work on it and submit patches. > > Dan > > > On Tuesday 28 September 2010 4:26:35 pm Kampf, Eric wrote: >> Hello, >> >> I would like to use CXF's Aegis data binding for a REST service (I have >> multiple reasons for preferring Aegis over JAXB...). The biggest >> impediment I face however is the presence of namespaces on all elements. >> This will be a hardship for most of our clients. >> >> I see that this topic came up a couple of years ago on this list: >> http://www.mail-archive.com/[email protected]/msg04683.html. >> It even resulted in the creation of a JIRA issue which is still listed as >> open: >> https://issues.apache.org/jira/browse/CXF-1291?page=com.atlassian.jira.plu >> gin.system.issuetabpanels:comment-tabpanel. >> >> Does anyone know if there is a solution for this? Our clients are simply >> not going to be able to use namespaces. Is there any hope of configuring >> Aegis to function without namespaces? >> >> Thanks. >> >> -Eric > > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog >
