On Mon, Jan 18, 2010 at 01:00:52PM +0000, James Strachan wrote:
> 2010/1/18 Jakub Podlesak <Jakub.Podlesak_at_sun.com>:
> >
> > RouteDefinition is a regular JAXB class:
> >
> > @XmlRootElement(name = "route")
> > @XmlType(propOrder = {"inputs", "outputs" })
> > @XmlAccessorType(XmlAccessType.PROPERTY)
> > public class RouteDefinition extends ProcessorDefinition<ProcessorDefinition> implements CamelContextAware {
> > ...
> >
> > is the jersey-json module, which should contain the required provider, activated?
>
> camel-web is dependent on jersey-json. The issue could be that jersey
> is not discovering jersey-json when its inside OSGi. i.e. the
> discovery of other JAXRS plugins maybe doesn't work in OSGi?
> (Typically jersey won't be able to see plugins in OSGi's class loader,
> so you need to use another mechanism in OSGi land like a bundle
> listener looking for new jersey extensions or something)
I am not sure what is the root cause as Charles bundles the jars and the issue was he had
misconfigured the Bundle-Classpath variable. Anyway, we are clearly
missing more tests to be confident certain things work with the OSGified
artifacts. I need to add these and will see.
Thanks for the feedback!
~Jakub
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fusesource.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
--
http://blogs.sun.com/japod