Ah, that's brilliant. Of course I just need to use the
ApplicationContext from within the constructor of my Jersey
application class, and grab the Spring configuration that I need. I'm
back up and running now, thanks!
public class MyApplication extends ResourceConfig {
public MyApplication() {
ApplicationContext rootCtx =
ContextLoader.getCurrentWebApplicationContext();
MyConfiguration myConfiguration =
rootCtx.getBean(MyConfiguration.class);
if (myConfiguration.isEnabled()) {
packages("com.mycompany.resources.whatever");
}
}
}
Mike.
On 8 January 2014 11:35, Jack Lista <jackalista_at_gmail.com> wrote:
> oops, sorry, here are the related imports:
>
> import org.glassfish.jersey.server.ResourceConfig;
> import org.springframework.context.ApplicationContext;
> import org.springframework.web.context.ContextLoader;
>
>
>
> On Wed, Jan 8, 2014 at 8:31 AM, Jack Lista <jackalista_at_gmail.com> wrote:
>>
>> You might try this, at least to see what's going on and what beans are in
>> your context, we also had fits with this stuff:
>>
>> public class FooApplication extends ResourceConfig {
>>
>> private static final Logger lager =
>> LoggerFactory.getLogger(FooApplication.class);
>>
>> public FooApplication() {
>>
>> lager.info("initializing.....");
>>
>> // tell Jersey where to find our jax-rs annotated classes
>> packages("com.ep.foo");
>>
>> ApplicationContext rootCtx =
>> ContextLoader.getCurrentWebApplicationContext();
>> String beans =
>> Arrays.asList(rootCtx.getBeanDefinitionNames()).toString().replace(',',
>> '\n');
>> lager.info("ROOT CTX:::" +beans+ ", beans.length(): "
>> +beans.length());
>> }
>>
>>
>> On Wed, Jan 8, 2014 at 6:59 AM, Michael Iles <michael.iles_at_gmail.com>
>> wrote:
>>>
>>> (Cross-posted to SO:
>>>
>>> http://stackoverflow.com/questions/20998983/how-to-initialize-jersey-application-resourceconfig-with-spring)
>>>
>>> I'm using Jersey 2 and Spring, and I'm trying to initialize my Jersey
>>> application (i.e. the class derived from ResourceConfig) with
>>> parameters from the Spring context.
>>>
>>> Background: I have a single Jersey application that I build (i.e. a
>>> single WAR) and I deploy it across a server cluster with different
>>> Spring configurations on different servers to enable or disable
>>> different parts of the server, e.g. some of the servers have /search
>>> resources turned on, etc. This was really easy in Jersey 1.0: I just
>>> put,
>>>
>>> <context:component-scan base-package="com.mycompany.resources.search"/>
>>>
>>> in a Spring config to have Jersey scan that particular package and
>>> enable the JAX-RS resource providers in it.
>>>
>>> Now in Jersey 2.0 the Spring <context:component-scan ... /> doesn't
>>> work, so resources have to be programmatically registered in a startup
>>> class derived from ResourceConfig:
>>>
>>> public class MyApplication extends ResourceConfig {
>>>
>>> public MyApplication() {
>>> packages("com.mycompany.resources.search");
>>> }
>>> }
>>>
>>> So far so good, but I need to conditionally scan that package, and I
>>> can't figure out how to get any Spring configuration into the
>>> MyApplication class. I thought that constructor injection might work:
>>>
>>> public class MyApplication extends ResourceConfig {
>>>
>>> @Autowired
>>> public MyApplication(@Qualifier("my-config") MyConfiguration
>>> myConfiguration) {
>>> if (myConfiguration.isEnabled()) {
>>> packages("com.mycompany.resources.search");
>>> }
>>> }
>>> }
>>>
>>> However HK2 complains that it can't find a default constructor to
>>> use... so this indicates to me that DI is in play in the construction
>>> of this class, but that the DI isn't using Spring.
>>>
>>> Similarly, using the the Spring bean lifecycle doesn't work:
>>>
>>> public class MyApplication extends ResourceConfig implements
>>> InitializingBean {
>>>
>>> @Autowired
>>> private MyConfiguration myConfiguration;
>>>
>>> public MyApplication() {
>>> }
>>>
>>> @Override
>>> public void afterPropertiesSet() throws Exception {
>>> if (myConfiguration.isEnabled()) {
>>> packages("com.mycompany.resources.search");
>>> }
>>> }
>>> }
>>>
>>> (The afterPropertiesSet method isn't called.)
>>>
>>> So now I'm stuck: is there any way to configuration a Jersey
>>> ResourceConfig application object using Spring?
>>>
>>>
>>> Thanks,
>>> Mike.
>>
>>
>