Hi Currently CXF JAX-RS installs all providers it supports from a start rather than loading them lazily, and AtomProvider which depends on Abdera is one of them. In fact, providing a custom Atom provider would be trivial, but I thought originally that by shipping a default one would kind of ensure that CXF JAX-RS is rock-solid with respect to supporting Atom due its dependency on the possibly best Atom implementation out there. Thus, rather than removing an atom provider from a default list I'd rather implement some lazy provider initialization policy at some time later on which would fix the issues like the one you see below...
May be the easiest way to fix the issue is just drop the Abdera 0.4.0 libs into a shared/libs or into your webapp/WEB_INF/libs, or dropping just some core Abdera libs (-core, parser, i18n) : a.. Core API: abdera.core.0.4.0-incubating.jar (required) a.. Parser Impl: abdera.parser.0.4.0-incubating.jar (required) a.. IRI Support: abdera.i18n.0.4.0-incubating.jar (required) If you were depending on the distribution then you wouldn't see this issue... Hope it helps, Sergey [1] http://cwiki.apache.org/confluence/display/ABDERA/Getting+Started ----- Original Message ----- From: "Matthew Pocock" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, May 22, 2008 7:39 AM Subject: Re: REST problems > By including axiom-impl as a dependency I have got past this, but now am > getting a new excepton about > org.apache.abdera.i18n.text.io.FilteredCharReader. > > I am confused. Any ideas? > > Matthew > ---------------------------- IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
