Hi Richard,
I am not 100 % sure i understand your question. I am confused with
the reference to Jersey 1. Anyway, to configure a specific ResourceConfig subclass
in your web application, you may want to use the following servlet init parameter in your web.xml descriptor:
javax.ws.rs.Application (see [1])
An example can be found at [2].
To achieve JAX-RS 2.0 portability, the referred application class
would directly extend the JAX-RS Application (as in [3]).
Please clarify if you asked for something else.
Thanks,
~Jakub
[1]
https://jersey.java.net/apidocs/2.1/jersey/org/glassfish/jersey/servlet/ServletProperties.html#JAXRS_APPLICATION_CLASS
[2]
https://github.com/jersey/jersey/blob/master/examples/helloworld-webapp/src/main/webapp/WEB-INF/web.xml
[3]
https://github.com/jersey/jersey/blob/master/examples/helloworld-webapp/src/main/java/org/glassfish/jersey/examples/helloworld/webapp/MyApplication.java
On Jul 26, 2013, at 8:07 PM, Richard Sand <rsand_at_idfconnect.com> wrote:
> Hey all - apologies for a newbie question - I'm using Jersey2 for the first
> time (I've used Jersey1.17 before) and am writing an app to be deployed on
> Tomcat7, and am trying to figure out how ResourceConfigs work. Typically to
> make my web apps portable between environments, I'd have a context-param in
> the web.xml holding the path to an external config file (which may be java
> properties, an xml config file, or such). What's the proper pattern for
> doing this technique in Jersey2?
>
> Thanks for any input!
>
> -Richard
>
>