On Dec 27, 2010, at 5:18 AM, Srinivas Naresh Bhimisetty wrote:
> That sounds to be proper.
> I'm not sure why this behavior is observed.
>
That error occurs because JSR 311 API 1.1 is in the class path,
specifically the version obtained from the maven central repo:
http://repo1.maven.org/maven2/javax/ws/rs/jsr311-api/1.1/
and 1.1.1 should be used instead. (Note that Jersey bundles JSR 311
API 1.1.1 311 in jersey-core)
History: the JAX-RS EG found a backwards compatibility issue that
needed to be fixed, but before that was fixed someone (not us) pushed
the artifacts to the maven central repo and once there they cannot be
removed, deprecated or updated.
Paul.
> - Naresh
>
> On Wed, Dec 22, 2010 at 12:51 AM, jliao <jliao_at_riotgames.com> wrote:
>
> I use "mvn eclipse:eclipse" to generate the libraries needed for the
> IDE.
> Here's the ones that shown in the build path inside the IDE that I
> believe
> are relevant:
>
> grizzly-framework-1.9.18.jar
> grizzly-http-servlet-1.9.18.jar
> grizzly-http-1.9.18.jar
> grizzly-portunif-1.9.18.jar
> grizzly-rcm-1.9.18.jar
> grizlly-servlet-webserver-1.9.18.jar
> grizzly-utils-1.9.18.jar
> jersey-spring-1.4.jar
> jersey-client-1.4.jar
> jersey-core-1.4.jar
> jersey-json-1.4.jar
> jersey-server-1.4.jar
> jersey-test-framework-core-1.4.jar
> jersey-test-framework-grizzly-1.4.jar
>
> BTW thanks for your patience and helps so far. :)
>
> --
> View this message in context: http://jersey.576304.n2.nabble.com/unit-test-jersey-rest-call-with-jersey-test-framework-tp5847765p5855826.html
> Sent from the Jersey mailing list archive at Nabble.com.
>