Support @Immediate services by default

[glassfishrobot]

HK2 has added a new feature called @Immediate services. These are services that are started as soon as they are bound into the system. It would be nice for Jersey to support this scope/context pair by default out of the box. This would be very similar to the PerThread scope/context pair that Jersey already supports out of the box.

Here is a request from the community to support this feature:

http://stackoverflow.com/questions/20713086/what-corresponds-to-aseagersingleton-in-hk2-in-jersey-2/20721765#20721765

Affected Versions

[2.5.1]

[glassfishrobot]

Reported by @jwells131313

[glassfishrobot]

Issue-Links:
is related to
JERSEY-2979

[glassfishrobot]

@AdamLindenthal said:
https://github.com/jersey/jersey/pull/173

[glassfishrobot]

@AdamLindenthal said:
Merged, thanks for contributing!

[glassfishrobot]

@AdamLindenthal said:
That was actually meant for Jord - the author of the pull request on github. To you, John, thanks for reporting !

[glassfishrobot]

svavra said:
We had to disable Immedate Scope HK2 feature due to several issues with ImmediateThreads (tracked as HK2-280). As a result, @Immediate services do not work by default anymore.

[glassfishrobot]

svavra said:
I just wanted to give it a quick shoot but without a success. With 2.4.0-b33, the problem still remains. Threads are left behind on application undeploy, and also jersey-client creation implies new thread for immediate services. I'm not saying though it won't be possible to do fine tuning and make it work in jersey by default. It will require more time than just an hour...

[glassfishrobot]

@jwells131313 said:
The changes needed for Jersey to enable Immediate scope by default have been in hk2 for a long time. Can someone please re-enable Immediate scope. Please see HK2-280 for more details

[glassfishrobot]

This issue was imported from java.net JIRA JERSEY-2291