In this particular case, it might be worth considering whether the particular use case holds water. 'Gee, I have these XMLBeans over here for some of my types, but I can't/don't want to bother to either build out XMLBeans for all of my types or build JAXB for those. Couldn't I mix and match? It seems incompletely crazy to me (and much like I've been learning about JAX-RS), but it also seems like a big job to do it coherently.
On Mon, Nov 3, 2008 at 8:40 AM, Glen Mazza <[EMAIL PROTECTED]> wrote: > > I share your sentiments that you placed in put in that bug report, namely > that CXF, like Metro, does not have a requirement or an architectural need > to do everything that XFire does. BTW, for the benefit of others, here's > the link: https://issues.apache.org/jira/browse/CXF-1891 > > > Benson Margulies-4 wrote: >> >> Any other committers care to weigh in on this? >> > > -- > View this message in context: > http://www.nabble.com/CXF-1891-another-revenant-from-XFire-tp20302600p20302927.html > Sent from the cxf-dev mailing list archive at Nabble.com. > >
