Will look at it as soon as possible.
Thanks,
Marek
On 05 Nov 2013, at 21:02, Miles, Eric (CONT) <Eric.Miles_at_capitalone.com> wrote:
> Thanks for the reply Marek, however I've since opened up a defect regarding my specific issue:
>
> https://java.net/jira/browse/JERSEY-2187
>
> Injecting the ServiceLocator and then calling getService(Class) does not resolve my issue, at least in this use case. Take a look at the details provided there.
>
> Thanks,
> Eric Miles
>
> From: Marek Potociar <marek.potociar_at_oracle.com>
> Reply-To: Jersey Users <users_at_jersey.java.net>
> Date: Tuesday, November 5, 2013 2:54 PM
> To: Jersey Users <users_at_jersey.java.net>
> Subject: [Jersey] Re: Spring/HK2/Jersey question
>
> You can inject the application wide ServiceLocator instance e.g. into your JAX-RS Application sub-class (or any other injectable component). See here:
> https://github.com/jersey/jersey/tree/master/tests/integration/spring3
>
> The above link points to an example + integration test for our current Spring 3.x integration via HK2.
>
> Marek
>
> On 30 Oct 2013, at 19:13, Miles, Eric (CONT) <Eric.Miles_at_capitalone.com> wrote:
>
>> All,
>>
>> I'm attempting to @Inject a Spring bean into an HK2 service (InjectionResolver) and am having some difficulty. I've attempted to follow the HK2 and Spring integration documentation at https://hk2.java.net/spring-bridge/ but what is the ServiceLocator name that Jersey uses? Are there numerous? If so, how does that impact registering the Spring/HK2 bridge?
>>
>> I realize there's been a lot of swirl the last 36 hours about JSR-330 and HK2. No opinion here, just need my problem solved.
>>
>> Thanks,
>> Eric
>>
>> The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
>
>
> The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.