Skip to content
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

Integration Issues with Queue-it in Spring Cloud Environment #13

Closed
NeeDKK opened this issue Aug 9, 2023 · 1 comment
Closed

Integration Issues with Queue-it in Spring Cloud Environment #13

NeeDKK opened this issue Aug 9, 2023 · 1 comment

Comments

@NeeDKK
Copy link

NeeDKK commented Aug 9, 2023

We are currently facing challenges integrating Queue-it into our system that is built on Spring Cloud. The demo code provided appears to be tailored for a Servlet-based environment, using javax.servlet.http.HttpServletRequest and HttpServletResponse.
However, in Spring Cloud, especially when working with Spring Cloud Gateway, the environment is reactive, utilizing classes like ServerHttpRequest and ServerHttpResponse. Attempting to cast these reactive classes to the servlet classes results in a casting error:"org.springframework.http.server.reactive.ReactorServerHttpRequest cannot be cast to javax.servlet.http.HttpServletRequest
"
This has created a roadblock in our integration efforts, as we cannot adapt the provided demo code to our non-servlet-based, reactive architecture.

Could you please provide guidance or examples of how we might integrate Queue-it within a Spring Cloud Gateway environment? Any assistance or best practices to follow in this particular scenario would be greatly appreciated.

Thank you for your attention to this matter. We look forward to your support in resolving this integration challenge.

@csmichaelkamal
Copy link

Hello NeeDKK

Thank you for reaching out to Queue-it.

Regarding the Java Connector compatibility issue with Spring boot 3, we want to inform you that we are working on it right now and will update you with the changes you need to make in order to be able to continue your work.

Please, note that the communication will be done via Queue-it support representative person

@Hesi01 Hesi01 closed this as completed Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants