Hi Ari,
Glad you solved it. OSGi dependencies can be so hard to debug...
hopefully we can make this easier when Jersey has better OSGi support.
Paul.
On Aug 28, 2009, at 11:27 AM, Ari Heino wrote:
>
> Ok, got this solved... finally :)
>
> We had a OSGi bundle class loading problem that caused this.
>
> originally we had:
> ----------------
> client bundle
> --> dependency to: library bundle
>
> server bundle
> --> dependency to: library bundle
>
> library bundle (exports all jersey JARs packages)
>
> now we have:
> -------------
> jaxb bundle (exports all jaxb API/Impl JARs packages)
> jaxen bundle (exports all jaxen-1.1.1.jar packages)
> annotation bundle (exports annotations-api.jar packages)
> jersey bundle (exports rest jersey dependency JARs packages, like
> abdera and
> http and so on)
>
> client + server bundles
> --> dependency to all above
>
> So, our environment was causing jersey to not see jaxb transformation
> providers.
>
> -- .aRi
>
> --
> View this message in context: http://n2.nabble.com/Abdera-Feeds-not-usable-in-Eclipse-OSGi-tp3472905p3533618.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
>