users@jersey.java.net

Re: [Jersey] Cannot Instantiate new provider

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Fri, 19 Jun 2009 14:52:13 +0200

On Jun 19, 2009, at 2:32 PM, Jonathan Cook - FM&T wrote:

> And if I upgrade is it just a case of changing jersey.jar to
> jersey-core1.0x.jar and jersey-core-1.0.x.jar or do all the
> dependencies
> need upgrading as well.

Sort of.... a fair bit has changed between 0.6 and 1.1.0-ea.

For version 0.8 and onwards we moved over to using maven. Plus we
changed some package names as well. For example, as of 1.0 and beyond
the TemplateProcessor now resides in the package:

   com.sun.jersey.spi.template.TemplateProcessor

See here for what you need for 1.0.3:

https://jersey.dev.java.net/source/browse/*checkout*/jersey/tags/jersey-1.0.3/jersey/dependencies.html
https://jersey.dev.java.net/nonav/apidocs/1.0.3/jersey/

See here for what you need for 1.1.0-ea

https://jersey.dev.java.net/source/browse/*checkout*/jersey/tags/jersey-1.0.3/jersey/dependencies.html

There are certain things to help ant users, like a jersey-bundle jar
which combined the set of required jersey jars, you can also download
a zip of the jersey jars (as described in the dependency document).

Hope this helps,
Paul.

>
>
> -----Original Message-----
> From: Paul.Sandoz_at_Sun.COM [mailto:Paul.Sandoz_at_Sun.COM]
> Sent: 19 June 2009 13:18
> To: Jonathan Cook - FM&T
> Subject: Re: [Jersey] Cannot Instantiate new provider
>
>
> On Jun 19, 2009, at 2:01 PM, Jonathan Cook - FM&T wrote:
>
>> Thanks.
>>
>> Any ideas then or should I stick to using the list?
>
> The list is best, but i thought you might be uncomfortable disclosing
> certain types of info, if so feel free to email me privately certain
> information if you think it will help solve things faster.
>
> I recommend trying to upgrade it at all possible.
>
> My guess is there is something about your remote deployment scenario
> where the dependency on the freemarker stuff is causing issues. You
> might want to try commenting out the freemarker stuff in the
> implementation just to see your template processor gets instantiated
> and
> invoked.
>
> Paul.
>
>>
>> Jon
>>
>> -----Original Message-----
>> From: Paul.Sandoz_at_Sun.COM [mailto:Paul.Sandoz_at_Sun.COM]
>> Sent: 19 June 2009 13:00
>> To: Jonathan Cook - FM&T
>> Subject: Re: [Jersey] Cannot Instantiate new provider
>>
>> Taking off list, just in case you do not want to disclose some
>> details.... let me know otherwise...
>>
>> On Jun 19, 2009, at 1:42 PM, Jonathan Cook - FM&T wrote:
>>
>>> Hi,
>>>
>>> It is a windows environment. Our deployment is manual. We copy over
>>> some folders/files. We don't have jersey installed as such the jars
>>> are just bundled with our release.
>>>
>>> We are using the same version of Jersey in both environments and it
>>> is
>>
>>> older than 1.0.2.
>>
>> I realized i got the version wrong, the warning error message
>> indicates version 0.6 or less.
>>
>>
>>> Why does it get to that line of code below?
>>
>> It is hard for me to help you because you are running a very old
>> version of Jersey. Can i suggest you upgrade?
>>
>> Paul.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>