Make HttpMessageConverterExtractor top level class [SPR-5808]

[spring-projects-issues]

Oliver Drotbohm opened SPR-5808 and commented

I'm trying to implement ETag based caching with the M3's RestTemplate. Therefore I would like to use the template's default message conversion functionality in case I get a 200 result but rather access an already existing instance on a 304 e.g. Thus it would be cool if I could just subclass HttpMessageConverterExtractor, apply decision logik and trigger cache access or superclass extraction logic.

---

Affects: 3.0 M3

Referenced from: commits f7bf613, 59e41a2

[spring-projects-issues]

Arjen Poutsma commented

I'll move the HttpMessageConverterExtractor to the top-level.

Also, I'd be interested in that ETag code. Can you share it with us?

[spring-projects-issues]

Arjen Poutsma commented

Done

[spring-projects-issues]

Oliver Drotbohm commented

Of course. Just picked up the code and will get my hands dirty completing the stuff.

[spring-projects-issues]

Oliver Drotbohm commented

Have opened another ticket #10491 to address the caching idea. Had trouble attaching the source code, see comments over there.