The property enableAsyncPublish set to true has no effect

[gurgelbrazil]

Hi All,

1. When I set this configuration:

   "rsp-ui.enableStartServerOnActivation": [
    {
      "id": "redhat.vscode-server-connector",
      "name": "Red Hat Server Connector",
      "startOnActivation": true,
      "rsp-ui.enableAsyncPublish": true
    }
  ]

 VSCode identify the settings and the setting is displayed in light blue and the description of the setting is displayed when I drag the mouse over the setting (it's a little irrelevant but the text is: "Specifies which RSP Server have to be automatically started during activation. If option is disabled, user will have to manually start the RSP Server through command palette or context menu"). 

2. When I set this configuration:

  "rsp-ui.enableAsyncPublish": true

VSCode does not identify the setting .. the setting is displayed in grayed blue and the text "Uknown Configuration Setting"  is displayed when I drag the mouse over.

Anyway, the server deploys  the application during initialization and not after initialization as defined by the setting. 

Any tips?

---

OS: Ubuntu
Kernel: 5.11.0-40-generic
VSCode Version: 1.62.3
RSP-ui version: redhat.vscode-rsp-ui-0.23.11

[robstryker]

async publishing means that the client (vscode) and rsp server (external process that vscode is a facade for) do not wait around for the publish to complete before returning. Essentially, the UI makes a rest to rsp-server to publish. rsp-ui will either issue the publish command to the backend via a synchronous api (ie, please do not return me a result until the operation completes) or asynchronously (rsp-server, please feel free to initiate the publish operation and let me know later when it completes, but return immediately if possible).

What exactly are you trying to get the tooling to do?

[gurgelbrazil]

Hello Rob.

I have two deployments: (1) A Datasource (....i know that it is almost deprecated :| ), and (2) a Java application (war).
The (huge) application takes about 5-10 minutes to deploy, so frequently the server is killed by the wildfly management-cli.

So, I expect using the enableAsyncPublish the server completes its startup process and then, the client demands the publish of the datasource and the application. But as I said, this property is not even recognized by any plug-ins ... in another computer (a windows machine), it works perfectly ....

Currently, I startup the server without the applciation, and after the startup, I deploy the application, but this procedure is too boring ...

[robstryker]

Ah, you're looking for a setting to deploy after startup. I don't think we have anything for that currently :| I can look into its feasibility.