Okay, thanks. It sounds like it's a buildr issue then. I'll check over with
them.
On Tue, Jul 26, 2011 at 8:19 AM, Jakub Podlesak
<jakub.podlesak_at_oracle.com>wrote:
> Hi Ian,
>
> i do not know anything about apache buildr, but
>
> com.sun.jersey.spi.container.**servlet.ServletContainer
> should be included in com.sun.jersey:jersey-server:**jar:1.8
> You need to get that jar onto your classpath.
>
> Maybe if you share your buildr files, someone from the list
> who is knowledgeable in buildr could help you.
>
> ~Jakub
>
>
>
> On 23.7.2011 18:19, Ian Nowland wrote:
>
>> Hi all,
>>
>> I've been trying to get a test project up and running, using an apache
>> buildr/Jersey setup, where I have the resources kick off in a web.xml using
>> a ServletContainer:
>>
>> <webapp>
>> <servlet>
>> <servlet-name>RPGProject Server</servlet-name>
>> <servlet-class>
>> com.sun.jersey.spi.container.**servlet.ServletContainer
>> </servlet-class>
>> <init-param>
>> <param-name>com.sun.jersey.**config.property.packages</**param-name>
>> <param-value>ianne.resources</**param-value>
>> </init-param>
>> <load-on-startup>1</load-on-**startup>
>> </servlet>
>> <servlet-mapping>
>> <servlet-name>RPGProject Server</servlet-name>
>> <url-pattern>/*</url-pattern>
>> </servlet-mapping>
>> </webapp>
>>
>> I recently upgraded pretty much everything in my system, (as well as wiped
>> out my maven repository), and unfortunately now when I try and run I'm
>> getting the following messages (with a whole stacktrace):
>>
>> 250 [btpool0-1] INFO org.mortbay.log - NO JSP Support for , did not find
>> org.apache.jasper.servlet.**JspServlet
>> 300 [btpool0-1] WARN org.mortbay.log - EXCEPTION
>> java.lang.**ClassNotFoundException: com.sun.jersey.spi.container.**
>> servlet.ServletContainer
>>
>> The dependencies I'm importing are:
>>
>> JERSEY = ['com.sun.jersey:jersey-**server:jar:1.8',
>> 'com.sun.jersey:jersey-core:**jar:1.8']
>> ASM = 'asm:asm-all:jar:3.3'
>> PERSISTANCE = 'javax.persistence:**persistence-api:jar:1.0.2'
>>
>> I know this might not be a Jersey issue (and instead would be buildr,
>> probably), but I thought I would ask here first. Am I missing some sort of
>> dependency, or does Jersey-server need to be referenced differently now or
>> something? Does anyone know what's going on here?
>>
>> Thanks,
>>
>> Ian
>>
>>
>>