You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (Jira)" <ji...@apache.org> on 2024/10/03 09:05:00 UTC
[jira] [Updated] (CAMEL-21311) NATS: Automatically added nats:// prefix in servers-parameter blocks the usage of NATS' built-in Websocket support
[ https://issues.apache.org/jira/browse/CAMEL-21311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Cosentino updated CAMEL-21311:
-------------------------------------
Fix Version/s: 4.9.0
> NATS: Automatically added nats:// prefix in servers-parameter blocks the usage of NATS' built-in Websocket support
> ------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-21311
> URL: https://issues.apache.org/jira/browse/CAMEL-21311
> Project: Camel
> Issue Type: Improvement
> Components: camel-nats
> Affects Versions: 4.8.0
> Reporter: Mikael Koskinen
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.9.0
>
>
> The current code in NatsConfiguration.java adds the nats:// -prefix automatically to the server connection string:
> String prefix = "nats://";
> This causes issues, because NATS supports other protocols like Websockets, where the prefix is ws:// or wss:// instead of nats://
> Looking at the examples provided by NATS, the prefix is something that the user of the NATS should provide as it defines the protocol between the client and the server. For example: [https://natsbyexample.com/examples/messaging/pub-sub/java]
> I was wondering if the auto-prefixing could be removed but then that would be a breaking change.
> Maybe a new configuration parameter could be added for defining the prefix (the protocol) and that could default to nats:// like currently?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)