Skip to content

Enabling "Push" functionality breaks annotated websocket servers #78

Closed
@kevinross

Description

The solution in #69 is intended to trigger this line so that Quarkus knows that websockets are used. Unfortunately, this conditional forces the builder to ignore any annotated server classes that are not also referenced by a config class (such as, but not limited to, the EnableWebsockets one). Therefore, if you have an annotated server class without also including a config class for it, quarkus drops your server from the build.

I can't do this myself here, but I've found a few breadcrumbs that might help with fixing it:

  • here is where server annotated endpoints are discovered
  • here is where those are used
  • it should be sufficient to produce an annotated endpoint builditem pointing to the atmosphere handler, to get the same result as EnableWebsockets

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions