Hi Charles,
Jersey does not currently work properly in an OSGi container.
Jakub is working on this, in a branch:
https://jersey.dev.java.net/svn/jersey/branches/jersey-servicemix
We need some help verify and testing this. If you have time would you
like to check out and build the branch and use the artifacts generated
from that?
Note that the class scanning to detect root resource and provider
classes is still an open issue with OSGi so you will need to
explicitly register those classes.
Paul.
On Jan 8, 2010, at 1:57 PM, cmoulliard wrote:
>
> When deploying Jersey project 1.1.5 in OSGI server running HTTP
> SErvice and
> jeety, I have the following error :
>
> 13:50:55,828 | INFO | l Console Thread |
> WebApplicationImpl |
> l.application.WebApplicationImpl 602 | Initiating Jersey application,
> version 'Jersey: 1.1.5-ea-SNAPSHOT 01/07/2010 02:57 PM'
> 13:50:55,859 | INFO | l Console Thread |
> PackagesResourceConfig |
> .api.core.PackagesResourceConfig 107 | Scanning for root resource and
> provider classes in the packages:
> org.apache.camel.web
> 13:50:55,875 | ERROR | l Console Thread |
> ProviderFactory |
> re.spi.component.ProviderFactory 190 | The provider class, class
> org.apache.camel.web.util.CamelResourceConfig, could not be
> instantiated.
> Processing will continue but the class will not be utilized
> com.sun.jersey.core.spi.scanning.ScannerException: The URI scheme
> bundle of
> the URI bundle://88.0:1/org/apache/camel/web is not supported. Package
> scanning deployment is not supported for such URIs.
> Try using a different deployment mechanism such as explicitly
> declaring root
> resource and provider classes using an extension of
> javax.ws.rs.core.Application
> at
> com
> .sun
> .jersey
> .core.spi.scanning.PackageNamesScanner.scan(PackageNamesScanner.java:
> 137)
> at
> com
> .sun
> .jersey
> .core.spi.scanning.PackageNamesScanner.scan(PackageNamesScanner.java:
> 121)
> at
> com
> .sun
> .jersey
> .api.core.ScanningResourceConfig.init(ScanningResourceConfig.java:69)
> at
> com
> .sun
> .jersey
> .api.core.PackagesResourceConfig.init(PackagesResourceConfig.java:110)
> at
> com
> .sun
> .jersey
> .api.core.PackagesResourceConfig.<init>(PackagesResourceConfig.java:
> 76)
> at
> com
> .sun
> .jersey
> .api.core.PackagesResourceConfig.<init>(PackagesResourceConfig.java:
> 87)
> at
> org
> .apache
> .camel.web.util.CamelResourceConfig.<init>(CamelResourceConfig.java:
> 37)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun
> .reflect
> .NativeConstructorAccessorImpl
> .newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun
> .reflect
> .DelegatingConstructorAccessorImpl
> .newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at java.lang.Class.newInstance0(Class.java:355)
> at java.lang.Class.newInstance(Class.java:308)
>
> Any idea How to avoid this ?
>
> Regards,
>
> Charles
> --
> View this message in context: http://n2.nabble.com/com-sun-jersey-core-spi-scanning-ScannerException-The-URI-scheme-bundle-of-the-URI-bundle-88-0-1-org-tp4272221p4272221.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
>