= WebSockets Next: Default serialization does not work in native mode In {ProductLongName} {ProductVersion}, when building and running applications with the `websockets-next` extension in native mode, the default serialization mechanism for WebSocket messages fails when using the `@OnTextMessage` lifecycle callback without a custom codec. This issue affects applications that rely on the default `JsonTextMessageCodec` for serializing and deserializing WebSocket messages. If a custom codec is specified using the `@OnTextMessage(codec = MyCodec.class)` annotation, the application works as expected. Workaround: link: https://quarkus.io/guides/writing-native-applications-tips#registering-for-reflection [Use the `@RegisterForReflection` annotation]. This issue is planned to be resolved in a future release. For more information, see link: https://issues.redhat.com/browse/QUARKUS-5981 [ QUARKUS-5981 ].