-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Javax WebSocket annotations not being used as default EndpointConfig #4407
Comments
lachlan-roberts
added a commit
that referenced
this issue
Dec 9, 2019
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts
added a commit
that referenced
this issue
Dec 13, 2019
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts
added a commit
that referenced
this issue
Dec 13, 2019
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts
added a commit
that referenced
this issue
Dec 13, 2019
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts
added a commit
that referenced
this issue
Dec 13, 2019
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
fixed with #4420 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version
10.0.x
Description
When adding an annotated endpoint with javax websockets given a specific EndpointConfig, the annotation configuration should be used as the default and any settings set in the provided EndpointConfig should override these default values.
Example:
This should result in an endpoint being added with:
uriTemplate = "/{end}/my/{point} (from manual endpoint config)
subprotocols = [ "end" ] (from manual endpoint config)
encoders = [ MyStringEncoder class reference ] (from annotation)
configurator = MyConfigurator class reference (from annotation)
The text was updated successfully, but these errors were encountered: