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

Updates for WebSocket 2.0 #157

Merged
merged 5 commits into from
Mar 24, 2020
Merged

Updates for WebSocket 2.0 #157

merged 5 commits into from
Mar 24, 2020

Conversation

markt-asf
Copy link
Contributor

The key changes are in the first commit.
The second fixes a build error.
The third and fourth are changes to the shared TCK infrastructure for Java 11 support.

I replaced the jakarta.websocket-api.jar and jakarta.servlet-api locally in glassfish with the M1 builds from Maven central to build this.

I ran the resulting TCK bundle against Apache Tomcat 10 implementation. The TCK passes when using both Java 8 and Java 11 with the exception of 2 tests which test behaviour which is ambiguously defined in the WebSocket spec.

The signature tests failed with Java 11 unless I replaced lib/sigtest.jar with the latest snapshot build
The error message in the logs was Unknown option -xjimage.

I'll be surprised if this PR is perfect first time around. Happy to adjust it as required after review.

Signed-off-by: Mark Thomas <markt@apache.org>
Signed-off-by: Mark Thomas <markt@apache.org>
Signed-off-by: Mark Thomas <markt@apache.org>
Signed-off-by: Mark Thomas <markt@apache.org>
@alwin-joseph
Copy link
Contributor

Hi Mark - I am making more signature file changes in #169. I will sync up my changes with respect to this this PR and other PRs with signature test changes . Thanks.

@alwin-joseph alwin-joseph merged commit 4096b43 into jakartaee:master Mar 24, 2020
@alwin-joseph alwin-joseph self-requested a review March 24, 2020 11:40
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.

2 participants