Paul Sandoz <Paul.Sandoz_at_Sun.COM> wrote:
The latter, so perhaps the naming is not appropriate. What would you
prefer ?
DynamicResourceConfig is fine, or maybe RuntimeResourceConfig
A ResourceConfig is a separate thing from a WebApplication and you may
want to dynamically add a new resource independently of the resource
config implementation. So i think it best to keep the things separate
and have methods exposed on WebApplication directly.
Do you require removal as well as addition of a resource class?
If I were to start a Jersey wish list, then yes :) I am working with a framework where I wish to dynamically "provision" individual resource classes to a web application "endpoint" without a container restart. I understand that the Jersey framework follows the JavaEE web application framework pattern of deploying a pre-defined set of artifacts as an atomic web application to a given container. My requirements may be outside the normal intended use of Jersey. I am content with maintaining my existing approach of managing the set of resource classes assigned to a Jersey web application and then just simply re-creating the web application if the set of resource classes changes, which should not occur often.
Thanks,
Aaron
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com