-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spring boot 3 #1680
Spring boot 3 #1680
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great effort @moscicky! 🥳 Very clean and smooth PR considering amount of changes required after Spring Boot upgrade.
/** | ||
* RestTemplateHermesSender. | ||
* | ||
* @deprecated as of Hermes 2.2.10, in favor of {@link pl.allegro.tech.hermes.client.webclient.WebClientHermesSender} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: I guess that we want to remove support for RestTemplateHermesSender
because we have a nice occasion for doing that by upgrading Hermes to new Spring Boot, right?
Or it was impossible to keep support for RestTemplateHermesSender
with newer Spring? I'm asking because not so long ago we had a discussion about RestTemplateHermesSender.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it impossible to keep support for RestTemplateHermesSender with newer Spring?
Yes. RestTemplateHermesSender
should have actually been called AsyncRestTemplateHermesSender
because it was using AsyncRestTemplateHermesSender
underneath. AsyncRestTemplate
was removed in spring boot 3. In theory we could switch to using regular RestTemplate
underneath but HermesSender
is inherently asynchronous:
public interface HermesSender {
CompletableFuture<HermesResponse> send(URI uri, HermesMessage message);
}
and RestTemplate
is sync. Imo its best to remove RestTemplateHermesSender
and encoure clients to migrate to WebClientSender
@@ -34,6 +34,9 @@ dependencies { | |||
implementation group: 'com.jayway.jsonpath', name: 'json-path', version: '2.5.0' | |||
implementation group: 'com.fasterxml.jackson.datatype', name: 'jackson-datatype-jsr310', version: versions.jackson | |||
|
|||
//TODO: remove after migrating from apache oltu |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion: Can we create an issue for migrating from Apache Oltu to other solution?
Maybe someone from Open Source community would be interested :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's already created :), see: #1679
...tion/src/integration/java/pl/allegro/tech/hermes/frontend/KafkaNamesMapperConfiguration.java
Outdated
Show resolved
Hide resolved
- except apache oltu related code
This PR:
spring boot
to 3.x.xjava ee
tojakarta
namespace (with the exception of jms related code)jetty
9 -> 11 (11 supportsjakarta
namespace, also required bywiremock 3.x
)wiremock
to version 3.beta which supportsjakarta
namespacehermes-client
withreactor
API changes: hermes-client is incompatible with Reactor 3.5 #1671AsyncRestTemplate
inhermes-client