On Mon, Jun 30, 2008 at 11:59:28AM +0200, Paul Sandoz wrote:
> Hi,
>
> I propose the following first steps to modularize Jersey.
>
> Split into three modules + one (in progress):
>
> jersey-core
> jersey-server
> jersey-client
>
> jersey-examples
As a part of modularizing effort, i suggest refactoring
also package names, so that it is clear what module
each package belongs to.
So far it was just:
com.sun.jersey.(api|impl|spi)
My suggestion would be to have:
com.sun.jersey.<module>.(api|impl|spi)
E.g. [com.sun.jersey.core.api] would belong to [jersey-core] module,
[com.sun.jersey.server.api] to [jersey-server] module, etc...
Thoughts?
~Jakub
>
> The jersey-core would contain all the shared stuff required for the
> client/server, which would include all the message body readers/
> writers, header reader/writers, IoC support etc.
>
> The jersey-server would contain all the server support, including all
> containers.
>
> The jersey-client would contain just the client support.
>
> I prefer doing this in a number of smaller iterative steps so that we
> always have something running. As part of this we also need to
> provide a jersey.jar bundle that contains everything (like Grizzly
> does) as well as the zip file. In addition providing source and
> javadoc to maven would be good.
>
> Does anybody know of a tool to recursively work about class
> dependencies from a set of classes. We could use that to determine
> the static compile-time dependencies for the client API and impl.
>
> Paul.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
--
http://blogs.sun.com/japod