RE: Registering Resource Classes (bootstrap)

From: Jerome Louvel <>
Date: Mon, 21 May 2007 16:41:58 +0200

Hi Paul,


> As Jerome mentions this also brings into question the dividing line
> between the container and the API. I think it would be good
> to specify
> something such that deployment can work with all the
> containers that are
> required to be supported by the JSR (and that can also be
> used by other
> containers) otherwise this will be a major pain point for
> developers if
> (by default) deployment is tied to a specific container. But
> we should
> rule (and i do not see how we can) the use of other deployment
> mechanisms if so desired.

I'm open to hear about a default deployment mechanism that would satisfy
most needs.

Maybe we can define some separate deployment mechanism for the Servlet and
the JAX-WS, or modify the Servlet spec to take JSR-311 into account. I'm
just concerned about putting in the API some features that are specific to
Servlet or JAX-WS views of the world (this would be true if we explicitly
supported Restlet).

Best regards,