Hi Ari,
See the dependencies document and the Atom section:
https://jersey.dev.java.net/source/browse/*checkout*/jersey/tags/jersey-1.1.1-ea/jersey/dependencies.html
and the type:
com.sun.jersey.atom.rome.impl.provider.entity.AtomFeedProvider
But i cannot guarantee you might run into similar class loading issues.
I am having a tricky time helping you because i do not understand
completely what your environment is. The errors you have presented
point to an issue of class loading, probably because the OSGi
environment is restricting access via the class loader available in
the thread current context.
Certainly your last error you presented indicates this, namely the
class loader cannot see the Woodstox implementation. Interestingly you
managed to get the Client to recognize FeedProvider by registering it
explicitly.
In your Eclipse / OSGi how are you defining what the dependencies are?
Perhaps asking on an Eclipse / OSGi forum might help?
Paul.
[1]
https://jersey.dev.java.net/source/browse/*checkout*/jersey/tags/jersey-1.1.1-ea/jersey/dependencies.html
On Aug 21, 2009, at 10:38 AM, Ari Heino wrote:
>
> In 1.1.1-ea samples (simple-atom-server) you are using
> com.sun.syndication.feed.WireFeed and
> com.sun.syndication.io.WireFeedInput
> objects on the server side to create the Feed and
> com.sun.syndication.feed.atom.Feed on the test class / client side
> to read
> the resource response.
>
> I'm only using org.apache.abdera.model.Feed.
>
> Should I be using those sun's classes? And in which Jar would I find
> them if
> they are needed to be used?
>
> .aRi
> --
> View this message in context: http://n2.nabble.com/Abdera-Feeds-not-usable-in-Eclipse-OSGi-tp3472905p3486934.html
> Sent from the Jersey mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>