[JERSEY-1841] ClientResponse.hasEntity() should not throw a NullPointerException Created: 11/Apr/13 Updated: 14/Nov/13 Resolved: 11/Nov/13
|Remaining Estimate:||0 minutes|
|Time Spent:||1 hour|
|Original Estimate:||3 hours|
The workaround is to check for getEntityInputStream() != null first, which is kind of awkward.
|Comment by Miroslav Fuksa [ 07/Nov/13 ]|
can you please provide more details? I cannot reproduce the NPE. I tried with 500 and 204 responses and never get NPE in ClientResponse.hasEntity(). I have tested it against 1.17 and with latest snapshot version. Exception stack trace and code example would help. The best would be simple maven project with test simulating the bug. Thanks.
I have the same problem with
|Comment by Miroslav Fuksa [ 11/Nov/13 ]|
I cannot reproduce the issue (I would need exception stack trace at least).