users@jersey.java.net

[Jersey] AnnotatedClassScanner - Best Practice

From: Cemo Koc <cem.koc.fwd_at_gmail.com>
Date: Fri, 2 Oct 2009 08:11:07 -0700 (PDT)

Hi all,

I am very newbie to JAX-RS. I have read all spec and documentation since
yesterday although dev.java.net has some serious issues.

I have two different maven modules and each has different dependencies.

Client side (com.x.y:client) has : jersey-client dependency

[INFO] +- com.sun.jersey:jersey-client:jar:1.0.3.1:compile
[INFO] | \- com.sun.jersey:jersey-core:jar:1.0.3.1:compile
[INFO] | \- javax.ws.rs:jsr311-api:jar:1.0:compile

Server side (com.x.y:server) has: jersey-server dependency and client
dependency
(Server side has resources.)

[INFO] +- com.sun.jersey:jersey-server:jar:1.0.3.1:compile
[INFO] | +- com.sun.jersey:jersey-core:jar:1.0.3.1:compile
[INFO] | | \- javax.ws.rs:jsr311-api:jar:1.0:compile
[INFO] | \- asm:asm:jar:3.1:compile
[INFO] +- com.x.y:client:jar:2.3.7:compile
[INFO] | \- com.sun.jersey:jersey-client:jar:1.0.1:compile

1. Is such implementation best practice in terms maven perspective?

2. This is about AnnotatedClassScanner which is used by our custom provider.
Where my custom provider implementation should be? In my case it is at
client side library because client side is referenced from Server side.

3. And If my implementation is right, I think that AnnotatedClassScanner
should be at jersey-core library. Because this class should have been
accessed from both Client Side and Server Side.

Thanks


-- 
View this message in context: http://n2.nabble.com/AnnotatedClassScanner-Best-Practice-tp3755924p3755924.html
Sent from the Jersey mailing list archive at Nabble.com.