I use jersey-spring and let Spring manage my resource classes and other
providers. Doing it that way "just works". I'm afraid I've never looked at
the helloworld sample, so I can't give you specific advice, but it sounds
like you're telling Jersey to instantiate TestInterface, which certainly
won't work. What happens when you give it your concrete class instead?
On Tue, Mar 22, 2011 at 4:19 PM, Cem Koc <cemalettin.koc_at_gmail.com> wrote:
> Hi,
>
> I have tried with jersey helloworld-app sample. I have such a log entry
>
> SEVERE: The following errors and warnings have been detected with resource
> and/or provider classes:
> SEVERE: The class com.sun.jersey.samples.helloworld.resources.TestInterface
> is an interface and cannot be instantiated.
>
> What kind of configuration you have?
>
> Thanks
>
> On 22 March 2011 18:08, zzantozz [via Jersey] <[hidden email]<http://user/SendEmail.jtp?type=node&node=6197997&i=0&by-user=t>
> > wrote:
>
>> What help do you need? That already works (annotating interfaces instead
>> of classes).
>
>
>
> ------------------------------
> View this message in context: Re: Interface as a resource<http://jersey.576304.n2.nabble.com/Interface-as-a-resource-tp6195227p6197997.html>
>
> Sent from the Jersey mailing list archive<http://jersey.576304.n2.nabble.com/>at Nabble.com.
>