users@jersey.java.net

[Jersey] Re: Extended WADL error after upgrading to 1.5

From: Ryan Stewart <rds6235_at_gmail.com>
Date: Thu, 10 Mar 2011 19:21:58 -0600

I saw this same problem. My solution was to move back to 1.4 for the time
being. It was still an upgrade from 1.2, where we started. I'd like to know
if there's a reasonable fix for this, as well.

On Thu, Mar 10, 2011 at 5:24 PM, Olson, Dan (LNG-CSP) <
dan.olson_at_lexisnexis.com> wrote:

> Hello:
>
>
>
> My project has been working with an extended WADL implementation. Today I
> upgraded to Jersey 1.5 and am receiving the following exception when
> requesting application.wadl. The WadlGeneratorConfig matches the samples
> (remember it worked before the upgrade).
>
>
>
> Please help!
>
>
>
> *HTTP ERROR 500*
>
> Problem accessing application.wadl. Reason:
>
>
> com.sun.jersey.api.wadl.config.WadlGeneratorConfig$WadlGeneratorConfigDescriptionBuilder.prop(Ljava/lang/String;Ljava/lang/Object;)Lcom/sun/jersey/api/wadl/config/WadlGeneratorConfig$WadlGeneratorConfigDescriptionBuilder;
>
> *Caused by:*
>
> java.lang.NoSuchMethodError:
> com.sun.jersey.api.wadl.config.WadlGeneratorConfig$WadlGeneratorConfigDescriptionBuilder.prop(Ljava/lang/String;Ljava/lang/Object;)Lcom/sun/jersey/api/wadl/config/WadlGeneratorConfig$WadlGeneratorConfigDescriptionBuilder;
>
> at myWadlGeneratorConfig.configure(myWadlGeneratorConfig.java:27)
>
>
>