Hi Nam,
Nam Nguyen wrote:
> Hi,
>
> I know that the Jersey client API will not be publicly available until
> 0.6, but I think it is not too early to raise point of consideration
> regarding partitioning Jersey packages. There could be some pure
> client that does not need any of the runtime classes. So I think its
> best if we could package client packages and shared packages in separate
> jars from the runtime packages.
>
Good point.
However, currently the client has some dependency on core functionality
from the runtime. It is not clear to me yet how much of dependency will
be retained as we develop the client side further, i want to reuse as
much code as possible (for example reuse the message reader/writer, URI
builder).
I think there is a larger point here about the client and the runtime.
The runtime also contains code for all containers, and i am sure not
everyone is interested in that. So maybe we need a more plugable
approach to packaging. I suspect Maven 2 might be able to help here to
separate out things into components.
Paul.
> -Nam
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: dev-help_at_jersey.dev.java.net
>
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109