Hi Charuka,
You can ignore that netty-transports.yml file. Carbon transport simply
provides a jar which you can use as a dependency. If you need to configure
it, the relevant netty configurations should be provided by the product
itself. You can add your own netty-transports.yml file with the
Hi all,
Any update on this? ${ballerina.home} variable is still present in the
latest release (v6.0.27). We are working on implementing a web socket in
Analytics Dashboard that requires to configure a HTTPS transport.
thanks,
Regards,
Charuka.
On Mon, Sep 18, 2017 at 11:19 AM, Thusitha Thilina
Hi Vinod,
In addition to what Sajith mentioned, shouldn't we move all the configs to
> the deployment.yaml, according to the C5 based config model[1]? Why are we
> having a separate config for netty?
AFAIK the idea is to move all the carbon-transport related configs to the
deployment.yaml. I
HI All,
In addition to what Sajith mentioned, shouldn't we move all the configs to
the deployment.yaml, according to the C5 based config model[1]? Why are we
having a separate config for netty?
[1] -
https://github.com/wso2/carbon-config/blob/master/docs/UpdatingConfigurations.md
On Mon, Sep 18,
Hi Sajith,
AFAIK with the redesign of carbon-transport, OSGi functionality is no
longer valid in transport. But IMHO we should fix this.
Thanks
Thusitha
On Mon, Sep 18, 2017 at 11:00 AM, SajithAR Ariyarathna
wrote:
> Hi All,
>
> I noticed $subject [1]. Any particular reason
On Mon, Sep 18, 2017 at 11:00 AM, SajithAR Ariyarathna
wrote:
> Hi All,
>
> I noticed $subject [1]. Any particular reason behind this?
>
> This Ballerina variable has been introduced in v4.2.3 and presents at the
> latest v6.0.7 too. IMO, this variable shouldn't be in the
>
Hi All,
I noticed $subject [1]. Any particular reason behind this?
This Ballerina variable has been introduced in v4.2.3 and presents at the
latest v6.0.7 too. IMO, this variable shouldn't be in the
netty-transports.yml as this is not a Ballerina repo.
[1]