Issue Details (XML | Word | Printable)

Key: JERSEY-2067
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: Miroslav Fuksa
Reporter: Miroslav Fuksa
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
jersey

Client filter instances are not injected

Created: 27/Aug/13 01:55 PM   Updated: 27/Sep/13 03:27 PM   Resolved: 25/Sep/13 03:42 PM
Component/s: None
Affects Version/s: None
Fix Version/s: 2.3

Time Tracking:
Original Estimate: 3 hours
Original Estimate - 3 hours
Remaining Estimate: 1 hour
Time Spent - 2 hours Remaining Estimate - 1 hour
Time Spent: 2 hours
Time Spent - 2 hours Remaining Estimate - 1 hour

Issue Links:
Related
 

Tags:
Participants: Miroslav Fuksa and Stefan Katerkamp


 Description  « Hide

When filter is registered as a instance into the client, the fileds of this instance are not injected.
Example:

public class MyFilter implements ClientRequestFilter {
	@Inject
	private Configuration config;
       
       ......
}

Register the filter on the client:
client.register(new MyFilter()).target()...

this cause that config field of MyFilter will never be injected.



Stefan Katerkamp added a comment - 27/Aug/13 03:40 PM

Please remove null check for config field in HttpDigestAuthFilter once this issue has been fixed.

See https://github.com/skaterkamp/jersey/blob/master/core-client/src/main/java/org/glassfish/jersey/client/filter/HttpDigestAuthFilter.java