Remove type from ResolverMapKey

[manofthepeace]

This is an attempt to fix #36067. The reproducer can still reproduce the issue by using different "types". Since the object mapper is per restclient, it should apply to any types used within it. The types should I believe not be checked.
With this attempt, the reproducer goes from 7 invocations to 2. I would appreciate help on finding out why it is still called twice.

reproducer: https://github.com/manofthepeace/quarkus-restclient-annotations-issue

Note: the type parameter is passed in a method chain that could potentially be cleaned up is this is the right approach, which I am not sure.

cc @geoand

many thanks,
Alex

[geoand]

Makes sense!

[manofthepeace]

@geoand I have found the cause of the why the@ClientObjectMapper was called twice. It is because the contextResolverMap existed in both ClientJacksonMessageBodyReader and ClientJacksonMessageBodyWriter. I think they can both use the same map as for both, the object mapper will be the same, as the annotation in the rest client does not specify if it is for reading or writing, in contrast to the server counterpart where ObjectReader and ObjectWriter can be specified separately.

I have added a second commit to get your opinion. I can adjust / squash if you find it is ok.

Before publishing the pr i'll try soaking it in my main app and see if it does what it should there. Seems ok after testing in my app.

Thank you.

[geoand]

Makes sense, thanks!

[quarkus-bot]

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

[quarkus-bot]

Milestone is already set for some of the items:

• Issue @ClientObjectMapper should run only once #36067

We haven't automatically updated the milestones for these items.

_{This message is automatically generated by a bot.}