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

fix: make sure annotated endpoints works along Vaadin PUSH #86

Merged
merged 3 commits into from
Dec 7, 2022

Conversation

mcollovati
Copy link
Contributor

Description

The workaround added to make PUSH work in Quarkus prevents the usage of custom annotated websocket endpoint. This change allows them to work along Vaadin PUSH.

Fixes #78

Type of change

  • Bugfix
  • Feature

Checklist

  • I have read the contribution guide: https://vaadin.com/docs/latest/guide/contributing/overview/
  • I have added a description following the guideline.
  • The issue is created in the corresponding repository and I have referenced it.
  • I have added tests to ensure my change is effective and works as intended.
  • New and existing tests are passing locally with my change.
  • I have performed self-review and corrected misspellings.

Additional for Feature type of change

  • Enhancement / new feature was discussed in a corresponding GitHub issue and Acceptance Criteria were created.

MarcinVaadin
MarcinVaadin previously approved these changes Oct 3, 2022
Copy link
Member

@MarcinVaadin MarcinVaadin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great that we now have covered custom web sockets with tests also on Quarkus. I've committed proposed changes to Flow, after releasing Flow with vaadin/flow#14694 we could remove JSR356_PATH_MAPPING_LENGTH from Quarkus.

mshabarov
mshabarov previously approved these changes Oct 4, 2022
The workaround added to make PUSH work in Quarkus prevents the usage of custom
annotated websocket endpoint. This change allow them to work along Vaadin PUSH.

Fixes #78
@mcollovati mcollovati force-pushed the issues/78_annotated_websockets branch from 210ac37 to a8b0366 Compare December 1, 2022 09:03
@mcollovati mcollovati marked this pull request as ready for review December 1, 2022 09:08
@mcollovati
Copy link
Contributor Author

Update the PR to be compatible with Vaadin 24. @MarcinVaadin @mshabarov Please review it again to check if it is all ok

@sonarcloud
Copy link

sonarcloud bot commented Dec 7, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@mshabarov mshabarov merged commit 74310d8 into master Dec 7, 2022
@mshabarov mshabarov deleted the issues/78_annotated_websockets branch December 7, 2022 08:09
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

Successfully merging this pull request may close these issues.

Enabling "Push" functionality breaks annotated websocket servers
3 participants